Hi Rich,
        My reasoning is that devices which need one of these entries are 
broken. Only someone who knows more that I about usb-storage should 
advocate adding an entry.

                                                        regards,

                                                        Stephen.

On Wed, 6 Mar 2002 [EMAIL PROTECTED] wrote:

> I think I might be able to guess why you feel this way but could you expand on your 
>opinion?  
> 
> I'm looking at it from an advanced-user/non-developer stand point, I have a piece of 
>hardware I need to make work.  I don't know enough to contribute to the code but I 
>can figure out enough to make it work within the framework of what the developer's 
>have built.  I don't think the type of user who says, "How do I use usb?" really 
>poses a problem since they probably have no idea what a kernel header file even is.  
>However there are dangerous users like myself, who know just enough to reverse 
>engineer well documented kernel code.  ;)
> 
> So are users like myself doing a service by sorting out previously unknown hardware 
>and reporting the results or are we doing a disservice?  I admit I don't know the 
>planning framework in usb-storage, is there an attempt to be device agnostic or is 
>the variability in products going to an ability to add new devices as they show up?
> 
> I'm not trying to start any flame war here I really do want to know so that I don't 
>unintentionally undermine the developers efforts.
> 
> Rich
> [EMAIL PROTECTED] wrote:
> > I don't think we should be encouraging people to add the the unusual device list.
> 
> On Wed, 6 Mar 2002 [EMAIL PROTECTED] wrote:
> 
> > I believe the faq and guide need a bit of expansion.  I finally stumbled onto what 
>has to be done regarding many usb-storage devices on the working devices list.  
>Namely, you probably will have to add an entry to unusual_devs.h in the usb-storage 
>module code, then recompile and reinstall the module.  I had to do this for a USB HD 
>I unwisely purchased without checking the list.  The things that need to be included 
>in the new entry are the vendor and device id's, the minor and major device revision 
>numbers [I used 0x0001 and 0xffff - ie every possible one], give names for the driver 
>to post, then you have to define protocols and flags - that's the hard part since if 
>you know as little as I do, you have to just empirically figure them out.  Look for 
>examples on the working devices list by searching for working usb-storage devices. 
>The protocol options are in usb.c, the flag options are in usb.h
> > 
> CLIP
> > 
> 
> 

-- 
 /------------------------------------+-------------------------\
|Stephen J. Gowdy                     | SLAC, MailStop 34,       |
|http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road,     |
|                                     | Menlo Park CA 94025, USA |
|EMail: [EMAIL PROTECTED]       | Tel: +1 650 926 3144     |
 \------------------------------------+-------------------------/


_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to