Phil Dibowitz wrote:
> Johann Wilhelm wrote:
>> This seems to be a really nice way...
>>
>> For my device disabling the cd-drive works very well.. but i got some
>> response from a guy that he only gets one tty-device.. maybe this can
>> fix this problem...
>>
>> it also seems the content of the cd
Joshua Church <[EMAIL PROTECTED]> wrote:
>
> patched against kernel 2.6.19.2 source
Joshua, sorry for the delay, I missed your original email somehow. Alan
pointed out that I never responded, so I'm finally getting back to you.
Regarding your patch, I have a few comments/questions:
1. You inclu
Johann Wilhelm wrote:
> This seems to be a really nice way...
>
> For my device disabling the cd-drive works very well.. but i got some
> response from a guy that he only gets one tty-device.. maybe this can
> fix this problem...
>
> it also seems the content of the cd-image is not the same on al
This seems to be a really nice way...
For my device disabling the cd-drive works very well.. but i got some
response from a guy that he only gets one tty-device.. maybe this can
fix this problem...
it also seems the content of the cd-image is not the same on all
devices.. my (branded) devic
Hi All,
IMHO, this patch should be removed... I'll explain the reasons:
1. Disabling the Virtual CD on that device does not assure that the
device turns the Serial Ports on, witch I believe was the primary
intention for this patch in the first place. One could get even better
results with
Robert Schedel wrote:
> Hello,
>
> please find attached a patch to make the external hard
> drive Teac HD-35PUK-B work with kernel 2.6.19 (here:
> 2.6.19-gentoo-r2). Originally, the drive is only sold
> with support for Windows/Mac.
Robert thanks for the info. At Alan's suggestion I combined your
Alan Stern wrote:
> On Wed, 27 Dec 2006, Robert Schedel wrote:
>
>> Hello,
>>
>> please find attached a patch to make the external hard
>> drive Teac HD-35PUK-B work with kernel 2.6.19 (here:
>> 2.6.19-gentoo-r2). Originally, the drive is only sold
>> with support for Windows/Mac.
>
>> + /* Repor
On Wed, 27 Dec 2006, Robert Schedel wrote:
> Hello,
>
> please find attached a patch to make the external hard
> drive Teac HD-35PUK-B work with kernel 2.6.19 (here:
> 2.6.19-gentoo-r2). Originally, the drive is only sold
> with support for Windows/Mac.
> + /* Reported by Robert Schedel <[EMAIL
Johann Wilhelm wrote:
> I have already sent the patch to the linux-usb maintainer in proper
> form... i searched at the wrong place for docs how to submit patches...
> sorry...
Ah - OK, I was out of the country for 10 days, so I may have missed that
copy of it.
> the virtual-cd-drive contains the
I have already sent the patch to the linux-usb maintainer in proper
form... i searched at the wrong place for docs how to submit
patches... sorry...
the virtual-cd-drive contains the windows drivers... and if the
virtual-cd-drive is enabled the modem-devices does not work... at
least with
Johann Wilhelm wrote:
> on my slackware11 the huawei e220 device is detected as mass storage
> device.. i found a way to prevent the kernel from this by adding it to
> the unusual_devs.h
I'm a bit confused - your comment in the patch mentions this can also be
used as a virtual CDROM drive - so you
On Παρ, 2006-08-25 at 00:22 -0700, Phil Dibowitz wrote:
> Emmanuel Vasilakis wrote:
> > Seems that the phone reports the memory stick size incorrectly, so the
> > following is needed to mount it:
> >
> > /* Reported by Emmanuel Vasilakis <[EMAIL PROTECTED]> */
> > UNUSUAL_DEV( 0x0fce, 0xe031, 0x0
Emmanuel Vasilakis wrote:
> Seems that the phone reports the memory stick size incorrectly, so the
> following is needed to mount it:
>
> /* Reported by Emmanuel Vasilakis <[EMAIL PROTECTED]> */
> UNUSUAL_DEV( 0x0fce, 0xe031, 0x, 0x,
> "Sony Ericsson",
> "M
Pete Zaitcev wrote:
> The stick replies to the door lock commands with a check condition
> (e.g. FAIL status in a normal bulk CSW), but the subsequent REQUEST SENSE
> returns all-zero sense. The situation is documented in our Bugzilla,
> including usbmon traces.
> https://bugzilla.redhat.com/bugzi
On Mon, 13 Dec 2004, william-robison wrote:
> Greetings:
>
> Here is another card reader that seems to benefit
> from an entry in unusual_devs. It is a 4 slot
> reader with a 3-port hub (USB2.0). Branded as
> PPA International model 1837.
> http://www.ppa-usa.com/product_pages/cardreaders/18
Alan Stern wrote:
On Tue, 14 Dec 2004, Phil Dibowitz wrote:
On a side note, are you okay with the 2nd half of the 2.4-cleanup patch
I submitted a few days ago -- the one that gets rid of the entries that
seemed to be unneeded after I removed the XLATE flags? Seems good to me,
but I split it int
Alan Stern wrote:
US_SC_SCSI, /* useProtocol */
US_PR_BULK, /* useTransport */
NULL, /* initFunction */
US_FL_FIX_INQUIRY), /* flags */
Are you submitting this for Linu
On Tue, 14 Dec 2004, Phil Dibowitz wrote:
> On a side note, are you okay with the 2nd half of the 2.4-cleanup patch
> I submitted a few days ago -- the one that gets rid of the entries that
> seemed to be unneeded after I removed the XLATE flags? Seems good to me,
> but I split it into two patc
Torsten Eriksson wrote:
I got this message when I plugged in a Lacie external USB hard drive.
Running Kernel 2.6.8.
Output from "dmesg":
Alrighty, sorry about that, time to try again.
Attached are two patches. The unusual_lacie should solve your problem,
Please let me know.
Additionally, there
On Mon, Oct 11, 2004 at 09:32:31PM -0700, Phil Dibowitz wrote:
> Torsten Eriksson wrote:
> >I got this message when I plugged in a Lacie external USB hard drive.
> >Running Kernel 2.6.8.
>
> Thanks. Try the following patch and let me know if you still get the
> message.
Erm. Actually, don't try
Torsten Eriksson wrote:
I got this message when I plugged in a Lacie external USB hard drive.
Running Kernel 2.6.8.
Thanks. Try the following patch and let me know if you still get the
message.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages
[Corrected a messed-up email address in Matt's message]
On Mon, 28 Jun 2004, Matthew Dharm wrote:
> The first thing to do is check the revision numbers reported by the two
> devices in question.
>
> Joel, does your system generate the 'unneeded entry' message?
>
> Matt
>
> On Mon, Jun 28, 2004
The first thing to do is check the revision numbers reported by the two
devices in question.
Joel, does your system generate the 'unneeded entry' message?
Matt
On Mon, Jun 28, 2004 at 05:02:41PM +0200, Jo?l Bourquard wrote:
> Hi Alan,
>
> That's a good question :-)
>
> There seem to be two dif
Hi Alan,
That's a good question :-)
There seem to be two different flavors of ISD-300 (ie: 05ab,0060)
devices, one of which needs this entry to work, and the other doesn't.
I have a 2 1/2'' HDD enclosure which (just like your device) doesn't
need the entry (so when I plug it, I get the same warn
On Fri, 25 Jun 2004, Michele G. wrote:
> usb-storage: This device (05ab,0060,1106 S 06 P 50) has unneededSubClass
> and Protocol entries in unusual_devs.h
Hmm... It looks like the entire entry is unnecessary. Does you device
still work okay with the patch below?
Jol, can you say why the entry
On Tue, 8 Jun 2004, Dan Scholnik wrote:
> On Mon, 2004-06-07 at 17:28, Alan Stern wrote:
> > Dan:
> >
> > By the way, I just noticed that the Casio QV unusual_devs.h entry has
> > US_FL_FIX_INQUIRY. Do you know why it's there, or if it's really
> > needed? Can you post a usb-storage debugging
On Mon, 2004-06-07 at 17:28, Alan Stern wrote:
> Dan:
>
> By the way, I just noticed that the Casio QV unusual_devs.h entry has
> US_FL_FIX_INQUIRY. Do you know why it's there, or if it's really
> needed? Can you post a usb-storage debugging log showing what happens
> when you remove that fla
Dan:
By the way, I just noticed that the Casio QV unusual_devs.h entry has
US_FL_FIX_INQUIRY. Do you know why it's there, or if it's really
needed? Can you post a usb-storage debugging log showing what happens
when you remove that flag?
(I have a long-running background project to remove as
On Tue, 2004-06-01 at 14:14, Alan Stern wrote:
> On Tue, 1 Jun 2004, Dan Scholnik wrote:
>
> > Up until the 2.6 kernels, there was one entry for all the QV cameras
> > with both US_SC_8070 and US_PR_CB that I think seemed to work fine for
> > everyone. As far as I know the only problem was all th
On Tue, 1 Jun 2004, Dan Scholnik wrote:
> Up until the 2.6 kernels, there was one entry for all the QV cameras
> with both US_SC_8070 and US_PR_CB that I think seemed to work fine for
> everyone. As far as I know the only problem was all the folks emailing
> the log entry stating that the Casio e
On Tue, 2004-06-01 at 11:11, Alan Stern wrote:
> On Mon, 31 May 2004, Dan Scholnik wrote:
>
> > Hi -
> >
> > Sorry to add to the Casio-induced headache, but...
> >
> > In february I sent in a patch to split the Casio QV entry in
> > unusual_devs.h into 2 entries, the first of which overr
On Mon, 31 May 2004, Dan Scholnik wrote:
> Hi -
>
> Sorry to add to the Casio-induced headache, but...
>
> In february I sent in a patch to split the Casio QV entry in
> unusual_devs.h into 2 entries, the first of which overrode both the
> protocol and the subclass to work around wha
Alan Stern wrote:
On Mon, 8 Dec 2003, Christian Strauf wrote:
Hi Alan,
Does your patch work if you leave out the FIX_INQUIRY flag or is that flag
necessary? Also, do you get any messages in your kernel log about
I need to test what happens if I leave out the FIX_INQUIRY flag. If I
set this t
As I am the original person who posted the patch, I would like to use
this opertunity to fix a few things. I have looked at the windows driver
.inf, and according to it, we should have the following: -
UNUSUAL_DEV( 0x0a17, 0x0004, 0x, 0x,
"Pentax",
"USB DI
On Mon, 8 Dec 2003, Christian Strauf wrote:
> Hi Alan,
>
> > Does your patch work if you leave out the FIX_INQUIRY flag or is that flag
> > necessary? Also, do you get any messages in your kernel log about
> I need to test what happens if I leave out the FIX_INQUIRY flag. If I
> set this to "0
Hi Alan,
> Does your patch work if you leave out the FIX_INQUIRY flag or is that flag
> necessary? Also, do you get any messages in your kernel log about
I need to test what happens if I leave out the FIX_INQUIRY flag. If I
set this to "0", what will the consequences be in the worst case? Will
On Mon, 8 Dec 2003, Christian Strauf wrote:
> Dear list,
>
> I would like to quickly drop in this patch against the vanilla linux
> 2.4.23 source tree which enabled the use of a Pentax Optio 330/430 RS
> digital camera as a mass storage device for me.
>
> I've been using this patch for quite som
37 matches
Mail list logo