Do you have a question? Post it now! No Registration Necessary
July 13, 2007, 1:27 am

hi all, as we known, linux kernel device driver have three layers:
bus, device and dirver.
but when a char device register, i will added to:
chrdevs[MAX_PROBE_HASH] and it seems dont blong to any bus.
does it means that the kernel only use the array
chrdevs[MAX_PROBE_HASH] to manager the driver and device?
for example, a usb driver and usb device will mach by ID, but when a
serial driver and serial device will mach by what ?
if a char deveice doesnt blong to any bus, how to traversal the
char devices?
the array of chrdevs[MAX_PROBE_HASH] doest EXPORT_SYMBOL
bus, device and dirver.
but when a char device register, i will added to:
chrdevs[MAX_PROBE_HASH] and it seems dont blong to any bus.
does it means that the kernel only use the array
chrdevs[MAX_PROBE_HASH] to manager the driver and device?
for example, a usb driver and usb device will mach by ID, but when a
serial driver and serial device will mach by what ?
if a char deveice doesnt blong to any bus, how to traversal the
char devices?
the array of chrdevs[MAX_PROBE_HASH] doest EXPORT_SYMBOL
Site Timeline
- » Porting linux kernel on Windriver SBC 7447 board.
- — Next thread in » Embedded Linux
-
- » File transfer / sharing between embedded linux version 2.6.8.1 and desktops (windows or li...
- — Previous thread in » Embedded Linux
-
- » Crosscompiling for ARM: reloc type R_ARM_ABS32 is not supported for PIC - ...
- — Newest thread in » Embedded Linux
-
- » Discrete floating current sensor
- — The site's Newest Thread. Posted in » Electronics Design
-
- » Sheesh
- — The site's Last Updated Thread. Posted in » Electronics Repair
-