> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Greg KH > Sent: Friday, May 30, 2003 9:50 PM > To: [EMAIL PROTECTED] > Subject: Re: [Linux-usb-users] Is there a USB Mass Storage > problems FAQ or HOWTO > > > - Programmers primarily like to write code. Since they are > doing this > because they want to, the fact that they don't write any > pretty user > documentation is no problem at all. If others view this as a > problem, it is their problem, not the original > developer's problem. >
I agree here... Developer write code, there is a lot of work to do here, so who is able to write useful lines of code must write code and not docs! (I'm a programmer, and I know that a programmer is not usually able to write anything understandable as documentation) > Now I get a _lot_ of user email about usb stuff on Linux. The problem that FAQ means frequently asked questions... So if that question are asked REALLY frequently... FAQ are done to help people to solve common and frequent problem. Forum must be for rarely seen problems. > Those emails > usually fall into the following categories: > - "I plugged my device in, now how do I use it?" This is a general > Linux question, as the same thing could be said for any kind of > device. The Linux USB Guide helps out just fine here for pointing > people which device node to connect to, and they are off and > running. > - "My USB device isn't assigned an address". This is a ACPI/PCI > interrupt routing issue that isn't the USB project's problem. I > point them at the "noapic" command line argument, and the ACPI > project, nothing much we can do there. It is an USB related problem. So a line in FAQ will not be so bad.... > - "My new wizzy USB device isn't supported by Linux." This is the > hardest, as Linux doesn't support a lot of different USB devices, > because we don't have the specs for the devices. This > includes the > wide range of usb-storage devices that decide to ignore the specs > and do their own thing... > Nothing to say here... The only reply to this could be "wait and hope" > So, in summary, the current Linux USB Guide works for the > first question > (which is the majority of my email.) The second question isn't a USB > problem at all, and the third can't really be fixed by any changes to > the USB Guide, right? > > So if you think there is some more documentation that needs to be > written, by all means, write away. Personally I don't see > much need for > any more, and I am one of the main people helping Linux USB users out > every day for the past few years. I suggest a line in the faq that mention the command as lspci -v and similar to include in a forum question. Too much people forget this, and first reply will alway be" what kernel? Lspci -v output?" etc. I will suggest also some lines about VIA chipset. This seems a common problem, with bulk transfers error, so it should be mentioned (I'm currently working on it, and I'll post something if I succeed) > Oh, as for the programming documentation, check out the 2.5 > kernel docs, > by running 'make psdocs'. It's quite good these days, thanks to the > effort of David Brownell. Also, any discrepancies noticed in > Documentation/usb/* would be nice to know, as they should be > fixed up if > there are any. > > Thanks again Brad for that Guide, it's a life saver for me. > > greg k-h ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
