On Fri, Nov 17, 2006 at 10:22:58AM -0500, Alan Stern wrote: > Those email addresse in unusual_devs.h are _not_ credits. (The credit > belongs to the person who writes and submits the patch, not the person > who owns the hardware and reports the problem.)
I think, "code generated from documentation" rule, can be applied here. CS theory, but i'm not a CS specialist ;-E > > I wish some day all this static useless id-ification will went to > > userspace. > > I do too. But there are difficulties with doing it. Just as one example, > consider trying to boot from a USB pendrive. At that point there _is_ no > userspace available to provide the blacklist entries! Do you mean usb flash drives? So, if yes. BIOS knows how to boot from it, right? Kernel isn't for itself, right? Thus, i think before (any) rootfs image is ready, use BIOS. If one is ready use userspace. --[not for further discussion, just note]-- I wanted (well, still want) to implement management char device for firmwares, Ids, and the like. I'm still looking forward it, as a way to merge two different worlds: sysops and kernel hackers. Devfs vs. udev shows all problems between two. Greg is doing OK, but he is longly on many kernel parts. I just submitted ez430 ids for ti_usb serial driver, and i see what that loneliness rusults in (just one example i saw is 12 pages of usb-serial.c:usb_serial_probe() with all that "horrible hacks" ); > Alan Stern > ____ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
