Thanks Alan,
It is good to get some feedback on how the buffer
manipulation should work. I appreciate you taking the
time.
>
> Did you take care about checking byte-endian issues?
>
Yep, I didn't take enough care. I thought I had, but I
have just found the URB transfer buffer is fragmented i
On Sun, 11 Mar 2007, Michael Cook wrote:
> Hi Alan,
>
> Thanks for your response. A bit more context... I dont
> have a choice in kernel release.
>
> I have the ISP1761 example driver which apparently works in
> 2.6.9 and I can't verify this as there isn't a
> configuration for 2.6.9 for my pla
Hi Alan,
Thanks for your response. A bit more context... I dont
have a choice in kernel release.
I have the ISP1761 example driver which apparently works in
2.6.9 and I can't verify this as there isn't a
configuration for 2.6.9 for my platform.
I have modified very little to get it to 2.6.14
On Sat, 10 Mar 2007, Michael Cook wrote:
> Hi,
>
> I'm trying to understand how the USB Mass Storage Device
> works in 2.6. Specifically 2.6.14. I see a fair amount of
> churn in this subsystem.
You didn't really ask any specific questions in your email -- you just
said you were curious about
Hi,
I'm trying to understand how the USB Mass Storage Device
works in 2.6. Specifically 2.6.14. I see a fair amount of
churn in this subsystem.
My principle concern/question is how does data from a file
on the filesystem get transported to a memory stick? I
have dumped info at many stages and
Hi Alan,
>> I have noticed an issue with writing to a USB mass storage device,
>> which is a flash-rom-based mp3 player.
>> [...]
>> I have verified that this issue still occurs with 2.6.6-rc1-bk4, as
>> requested by Andrew Morton. This error was never noticed in any
>> kernel v2.6.3 or less;
On Tue, 20 Apr 2004, Roberts-Thomson, James wrote:
> Hi,
>
> I have noticed an issue with writing to a USB mass storage device, which is
> a flash-rom-based mp3 player.
>
> I first noticed this issue with kernel 2.6.5 and the -mm6 patchset. I have
> verified that this issue still occurs with 2.
Hi,
I have noticed an issue with writing to a USB mass storage device, which is
a flash-rom-based mp3 player.
I first noticed this issue with kernel 2.6.5 and the -mm6 patchset. I have
verified that this issue still occurs with 2.6.6-rc1-bk4, as requested by
Andrew Morton. This error was never
I feel a bit of a fool, I was trying to mount sda1, which is where my
other flash drive mounts, I tried it with sda and it worked like a charm.
Thanks for the help!
Cameron Morrison
Matthew Dharm wrote:
What mount command are you using? Are you trying to mount sda1 or sda?
Regardless, can you
What mount command are you using? Are you trying to mount sda1 or sda?
Regardless, can you try the other one?
Matt
On Wed, Jul 09, 2003 at 05:10:17PM +1000, Cameron Morrison wrote:
> Alan Stern wrote:
> > On Tue, 8 Jul 2003, Cameron Morrison wrote:
> >
> >
> >>Hi,
> >>
> >>I've got an 128MB A
What kernel is this from?
According to this log, the READ commands are requesting a block address
that makes no sense at all -- it almost looks like random garbage.
One read does seem to work though... It's possible that the format of the
data isn't quite right, so the filesystem layer is getting
Alan Stern wrote:
On Tue, 8 Jul 2003, Cameron Morrison wrote:
Hi,
I've got an 128MB Apacer "Handy Steno 2.0" usb flash drive
(http://www.apacer.com/apacer_english/product_html/handy_steno20.asp).
It's giving the following error when i try to mount it : -
Attached scsi removable disk sda at scsi0
On Tue, 8 Jul 2003, Cameron Morrison wrote:
> Hi,
>
> I've got an 128MB Apacer "Handy Steno 2.0" usb flash drive
> (http://www.apacer.com/apacer_english/product_html/handy_steno20.asp).
> It's giving the following error when i try to mount it : -
>
> Attached scsi removable disk sda at scsi0, ch
Hi,
I've got an 128MB Apacer "Handy Steno 2.0" usb flash drive
(http://www.apacer.com/apacer_english/product_html/handy_steno20.asp).
It's giving the following error when i try to mount it : -
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 253949 512-byte hdwr s
on 5.0.2
> > > Date: Tue, 13 Nov 2001 10:05:29 -0600
> > > To: [EMAIL PROTECTED]
> > > From: Spectrum Digital Sales <[EMAIL PROTECTED]>
> > > Subject: Fwd: [[EMAIL PROTECTED]: [linux-usb-devel] USB
> > > mass storage device]
> > >
> > &
t;
To: "Astrid Wonner" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 7:19 PM
Subject: Re: [linux-usb-devel] USB mass storage device
boot.msg
Description: Binary data
messages
Description: Binary data
Sounds like the device isn't returning proper INQUIRY data. I've seen that
before. It's uncommon, but apparently works somehow with Windows. My
guess is that the Windows driver assumes random-access unless told
otherwise.
Can you recompile your kernel with usb-storage verbose debugging turned
Hello everyone,
I'm a newbie in kernel hacking and USB and I hope, you or your mailing list
can help me.
I have to write a driver for a USB device, that is recognized as a mass
storage device and can be used as such under Windows with the standard built-in
driver. In fact, it's an Evaluat
18 matches
Mail list logo
