On Thu, 1 Jun 2006, linux-os (Dick Johnson) wrote:
> >> Yes, it sounds like we're being non-real-worldly here. This change
> >> apparently broke things. Did it actually fix anything as well?
> >
> > Yes. At least, I think so. The change directly addresses a complaint
> > filed here:
> >
> > ht
On Thu, 1 Jun 2006 10:58:43 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> As an alternative, we could allow an "over-budget window" of say 10%.
That, plus we should provide a suitable i-know-what-im-doing user override,
with the appropriate warnings, as well as a printk which directs user
On Thu, Jun 01, 2006 at 10:58:43AM -0400, Alan Stern wrote:
> On Thu, 1 Jun 2006, Andrew Morton wrote:
>
> > On Thu, 01 Jun 2006 02:18:20 -0700
> > David Liontooth <[EMAIL PROTECTED]> wrote:
> >
> > > Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> > > hubs. Alan Stern ex
Am Donnerstag, 1. Juni 2006 17:09 schrieb linux-os (Dick Johnson):
> Many, most, perhaps all such devices don't take more power when they
> are "enabled". Everything is already running and sucking up maximum
> current when you plug it in! If the motherboard didn't smoke when
If they do, they are v
On Thu, Jun 01, 2006 at 11:09:46AM -0400, linux-os (Dick Johnson) wrote:
> Many, most, perhaps all such devices don't take more power when they
> are "enabled". Everything is already running and sucking up maximum
> current when you plug it in! If the motherboard didn't smoke when
> the device was
On Thu, 1 Jun 2006, Alan Stern wrote:
> On Thu, 1 Jun 2006, Andrew Morton wrote:
>
>> On Thu, 01 Jun 2006 02:18:20 -0700
>> David Liontooth <[EMAIL PROTECTED]> wrote:
>>
>>> Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
>>> hubs. Alan Stern explains,
>>>
>>> "The idea is
On Thu, 1 Jun 2006, Andrew Morton wrote:
> On Thu, 01 Jun 2006 02:18:20 -0700
> David Liontooth <[EMAIL PROTECTED]> wrote:
>
> > Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> > hubs. Alan Stern explains,
> >
> > "The idea is that the kernel now keeps track of USB power
Andrew Morton wrote:
(added linux-usb cc)
Yes, it sounds like we're being non-real-worldly here. This change
apparently broke things. Did it actually fix anything as well?
Gentoo recieved several reports of this. It appears that certain vendors
are worse than others (Verbatim flash drives a
On Thu, 01 Jun 2006 02:18:20 -0700
David Liontooth <[EMAIL PROTECTED]> wrote:
> Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> hubs. Alan Stern explains,
>
> "The idea is that the kernel now keeps track of USB power budgets. When a
> bus-powered device requires more cu
On Wed, May 31, 2006 at 11:38:28PM +0200, Frank Gevaerts wrote:
> On Tue, May 30, 2006 at 11:33:27AM -0700, Pete Zaitcev wrote:
> >
> > Please get rid of the above.
> > >* shut down bulk read and write
>
> OK, So here's the corrected patch:
>
> Signed-off-by: Frank Gevaerts <[EMAIL PROTECTED
On Tue, May 30, 2006 at 11:33:27AM -0700, Pete Zaitcev wrote:
>
> Please get rid of the above.
> > * shut down bulk read and write
OK, So here's the corrected patch:
Signed-off-by: Frank Gevaerts <[EMAIL PROTECTED]>
diff -pur linux-2.6.17-rc4/drivers/usb/serial/ipaq.c
linux-2.6.17-rc4.te
On Wed, May 31, 2006 at 06:10:42PM -0300, Luiz Fernando N. Capitulino wrote:
> On Tue, 30 May 2006 23:36:35 +0200
> Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> | On Tue, May 30, 2006 at 05:52:08PM -0300, Luiz Fernando N. Capitulino wrote:
> | > On Tue, 30 May 2006 19:48:21 +0200
> | > Frank Geva
On Tue, 30 May 2006 23:36:35 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Tue, May 30, 2006 at 05:52:08PM -0300, Luiz Fernando N. Capitulino wrote:
| > On Tue, 30 May 2006 19:48:21 +0200
| > Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| >
| > | On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz
On Tue, May 30, 2006 at 05:52:08PM -0300, Luiz Fernando N. Capitulino wrote:
> On Tue, 30 May 2006 19:48:21 +0200
> Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> | On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz Fernando N. Capitulino wrote:
> | > On Tue, 30 May 2006 11:38:01 -0300
> | > "Luiz Fern
On Tue, 30 May 2006 11:33:27 -0700
Pete Zaitcev <[EMAIL PROTECTED]> wrote:
| > @@ -967,3 +971,6 @@ MODULE_PARM_DESC(vendor, "User specified
| >
| > module_param(product, ushort, 0);
| > MODULE_PARM_DESC(product, "User specified USB idProduct");
| > +
| > +module_param(connect_retries, int, KP_
On Tue, 30 May 2006 19:48:21 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz Fernando N. Capitulino wrote:
| > On Tue, 30 May 2006 11:38:01 -0300
| > "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
| >
| > If it ran _before_ the timeout e
On Tue, May 30, 2006 at 11:33:27AM -0700, Pete Zaitcev wrote:
> On Tue, 30 May 2006 19:48:21 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> +0100
> > +++ linux-2.6.17-rc4.test/drivers/usb/serial/ipaq.c 2006-05-30
> > 19:41:19.0 +0200
> > @@ -692,6 +694,7 @@ static void ipaq_close(struc
On Tue, 30 May 2006 19:48:21 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
+0100
> +++ linux-2.6.17-rc4.test/drivers/usb/serial/ipaq.c 2006-05-30
> 19:41:19.0 +0200
> @@ -692,6 +694,7 @@ static void ipaq_close(struct usb_serial
> struct ipaq_private *priv = usb_get_serial_po
On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz Fernando N. Capitulino wrote:
> On Tue, 30 May 2006 11:38:01 -0300
> "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
>
> If it ran _before_ the timeout expires with no timeout error it does not
> depend. Then we can do the simpler solution:
On Tue, 30 May 2006 17:06:27 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Tue, May 30, 2006 at 11:38:01AM -0300, Luiz Fernando N. Capitulino wrote:
| > On Tue, 30 May 2006 10:21:41 +0200
| > Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| >
| > | On Mon, May 29, 2006 at 07:33:30PM -0300, Luiz
On Tue, May 30, 2006 at 11:53:29AM -0300, Luiz Fernando N. Capitulino wrote:
> On Tue, 30 May 2006 11:38:01 -0300
> "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
>
> | On Tue, 30 May 2006 10:21:41 +0200
> | Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> |
> | | On Mon, May 29, 2006 at 07:
On Tue, May 30, 2006 at 11:38:01AM -0300, Luiz Fernando N. Capitulino wrote:
> On Tue, 30 May 2006 10:21:41 +0200
> Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> | On Mon, May 29, 2006 at 07:33:30PM -0300, Luiz Fernando N. Capitulino wrote:
> | > On Mon, 29 May 2006 22:47:24 +0200
> | > I see.
>
On Tue, 30 May 2006 11:38:01 -0300
"Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
| On Tue, 30 May 2006 10:21:41 +0200
| Frank Gevaerts <[EMAIL PROTECTED]> wrote:
|
| | On Mon, May 29, 2006 at 07:33:30PM -0300, Luiz Fernando N. Capitulino wrote:
| | > On Mon, 29 May 2006 22:47:24 +0200
On Tue, 30 May 2006 10:21:41 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Mon, May 29, 2006 at 07:33:30PM -0300, Luiz Fernando N. Capitulino wrote:
| > On Mon, 29 May 2006 22:47:24 +0200
| > Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| > |
| > | The panic was caused by the read urb being s
On Mon, May 29, 2006 at 07:33:30PM -0300, Luiz Fernando N. Capitulino wrote:
> On Mon, 29 May 2006 22:47:24 +0200
> Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> |
> | The panic was caused by the read urb being submitten in ipaq_open,
> | regardless of success, and never killed in case of failure. W
On Mon, 29 May 2006 22:47:24 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Mon, May 29, 2006 at 05:24:10PM -0300, Luiz Fernando N. Capitulino wrote:
| > On Mon, 29 May 2006 21:43:35 +0200
| > Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| >
| > | On Mon, May 29, 2006 at 02:11:10PM -0300, Luiz
On Mon, May 29, 2006 at 05:24:10PM -0300, Luiz Fernando N. Capitulino wrote:
> On Mon, 29 May 2006 21:43:35 +0200
> Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> | On Mon, May 29, 2006 at 02:11:10PM -0300, Luiz Fernando N. Capitulino wrote:
> | >
> | > Frank, could you try this one please?
> | >
On Mon, 29 May 2006 21:43:35 +0200
Frank Gevaerts <[EMAIL PROTECTED]> wrote:
| On Mon, May 29, 2006 at 02:11:10PM -0300, Luiz Fernando N. Capitulino wrote:
| >
| > Frank, could you try this one please?
| >
| > I have no sure whether this makes sense, but every USB-Serial driver
| > I know exit
On Mon, May 29, 2006 at 02:11:10PM -0300, Luiz Fernando N. Capitulino wrote:
>
> Frank, could you try this one please?
>
> I have no sure whether this makes sense, but every USB-Serial driver
> I know exits in the write URB callback if the URB got an error.
It looks sane to me at least.
The ma
On Mon, 29 May 2006 13:25:53 -0300
"Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
| On Mon, 29 May 2006 12:01:02 -0300
| "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
|
| |
| | Hi Pete,
| |
| | On Fri, 26 May 2006 13:34:10 -0700
| | Pete Zaitcev <[EMAIL PROTECTED]> wrote:
On Mon, 29 May 2006 12:01:02 -0300
"Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
|
| Hi Pete,
|
| On Fri, 26 May 2006 13:34:10 -0700
| Pete Zaitcev <[EMAIL PROTECTED]> wrote:
|
| | On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]>
wrote:
| |
| | > usb 1-4.5.7:
Hi Pete,
On Fri, 26 May 2006 13:34:10 -0700
Pete Zaitcev <[EMAIL PROTECTED]> wrote:
| On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
|
| > usb 1-4.5.7: USB disconnect, address 79
| > [ cut here ]
| > kernel BUG at kernel/workqueue.c:110!
|
On Fri, May 26, 2006 at 01:34:10PM -0700, Pete Zaitcev wrote:
> On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> > usb 1-4.5.7: USB disconnect, address 79
> > [ cut here ]
> > kernel BUG at kernel/workqueue.c:110!
>
> Please let me know if
On Fri, May 26, 2006 at 01:34:10PM -0700, Pete Zaitcev wrote:
> On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
>
> > usb 1-4.5.7: USB disconnect, address 79
> > [ cut here ]
> > kernel BUG at kernel/workqueue.c:110!
>
> Please let me know if
On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote:
> usb 1-4.5.7: USB disconnect, address 79
> [ cut here ]
> kernel BUG at kernel/workqueue.c:110!
Please let me know if this helps:
--- linux-2.6.17-rc2/drivers/usb/serial/usb-serial.c2006-04
Alan Stern wrote:
> On Thu, 25 May 2006, Phil Dibowitz wrote:
>
>> @@ -115,10 +115,12 @@ static int slave_configure(struct scsi_d
>> /* According to the technical support people at Genesys Logic,
>> * devices using their chips have problems transferring more than
>> * 32
On Thu, 25 May 2006, Phil Dibowitz wrote:
> @@ -115,10 +115,12 @@ static int slave_configure(struct scsi_d
> /* According to the technical support people at Genesys Logic,
> * devices using their chips have problems transferring more than
> * 32 KB at a time. In practice
Phil Dibowitz wrote:
> Phil Dibowitz wrote:
>> It sounds like we have a consensus then. I'll try to get a patch to:
>>
>> - Add a MAX_SECTORS_64 flag
>> - Incorporate Benjamin's device
>> - Remove the Genesys logic (this will be the second genesys special-case that
>> I've replaced with a flag ;)
Phil Dibowitz wrote:
> It sounds like we have a consensus then. I'll try to get a patch to:
>
> - Add a MAX_SECTORS_64 flag
> - Incorporate Benjamin's device
> - Remove the Genesys logic (this will be the second genesys special-case that
> I've replaced with a flag ;) )
>
> Shouldn't take me ve
On Thu, 25 May 2006 02:15:37 -0500, Al Borchers <[EMAIL PROTECTED]> wrote:
> One minor thing, I would prefer "sizeof(string)" to "30", but
> it is not crucial.
Done in my tree. I'll either send a follow-up to Greg or resend, depending
on the acceptance.
-- Pete
Pete --
Thanks for checking with us. Looks good to me.
One minor thing, I would prefer "sizeof(string)" to "30", but
it is not crucial.
-- Al
Quoting Pete Zaitcev <[EMAIL PROTECTED]>:
> Clean up the unicode handling in io_edgeport. Make get_string size-limited.
>
> Signed-off-by: Pete Zaitcev
On Mon, May 22, 2006 at 04:30:48PM +0200, Frank Gevaerts wrote:
> Hi,
>
> We are having problems with the usb-serial ipaq driver in 2.6.16 (debian
> backports 2.6.16-1-686, but also reproducible with self-compiled
> kernel.org kernel)
>
> Sometimes, we get the following on disconnect:
Can you
On Thu, Mar 16, 2006 at 12:49:18AM +0100, Adrian Bunk wrote:
> > A lot of this is BIOS dependant and if we can isolate cases where one
> > BIOS works and another doesn't an lspci -vvxxx would be helpful so we
> > can look for chipset pokery
>
> It's below.
Vendor fix went to the ide maintainer an
On Fri, 12 May 2006 21:32:39 -0700, David Brownell <[EMAIL PROTECTED]> wrote:
> Can you confirm that this patch also resolves your issue? [...]
I noticed that you added the mask inside the case while Nathan
added it outside. So, he did it for all nVidia silicon.
I would think it may be better if
Thanks for the patch. However, did you not get my very last message?
Checking back through my mail logs, I think it might not have been
delivered.
After claiming that the dma mask fixed the problem, I quickly
discovered that the dma was not what did it. Thus the patch you sent
does not work.
B
On Fri, May 12, 2006 at 02:16:04PM -0400, Alan Stern wrote:
> On Wed, 10 May 2006, Vojtech Pavlik wrote:
>
> > On Wed, May 10, 2006 at 10:50:47AM -0400, Alan Stern wrote:
> > > Dmitry and Vojtech:
> > >
> > > So many USB keyboards require the HID_QUIRK_NOGET blacklist flag, does it
> > > make se
On Tuesday 09 May 2006 10:37 pm, Nathan Becker wrote:
> I added 1 line to drivers/usb/host/ehci-pci.c which sets the DMA mask,
> and now it seems to work with ehci loaded and with 4 GB of RAM.
> Unfortunately, I don't really understand what I did. Perhaps you have
> a better idea what this is doin
On Wed, 10 May 2006, Vojtech Pavlik wrote:
> On Wed, May 10, 2006 at 10:50:47AM -0400, Alan Stern wrote:
> > Dmitry and Vojtech:
> >
> > So many USB keyboards require the HID_QUIRK_NOGET blacklist flag, does it
> > make sense to set the flag automatically for every keyboard device?
> >
> > Or w
On Wed, May 10, 2006 at 10:50:47AM -0400, Alan Stern wrote:
> Dmitry and Vojtech:
>
> So many USB keyboards require the HID_QUIRK_NOGET blacklist flag, does it
> make sense to set the flag automatically for every keyboard device?
>
> Or would that cause problems with some highly advanced keyboar
Like I said in my previous message, I am not a kernel developer. I am
a programmer though, so I thought I'd give your suggestions a try.
I added 1 line to drivers/usb/host/ehci-pci.c which sets the DMA mask,
and now it seems to work with ehci loaded and with 4 GB of RAM.
Unfortunately, I don't r
Thanks for all suggestions. I tried passing mem=2048m to the kernel.
This is with 2.6.16.13. This did fix the USB ehci problem. Of course
the kernel only sees half of my RAM, so this is not a satisfactory
long-term workaround.
As for your other suggestions, I'm not sure how to implement those
On Thursday 04 May 2006 10:46 pm, Nathan Becker wrote:
> Yes, GART_IOMMU is already turned on. Do you want me to send more
> detailed debugging messages?
And when you tell the kernel to only use 2 GB, it works again right?
Just trying to rule out hardware or hardware-init bugs.
Maybe you could c
> On Wed, May 03, 2006 at 09:52:11PM -0700, Nathan Becker wrote:
> > Hi,
> >
> > I recently added two more memory modules to my Gigabyte K8NXP-SLI
> > motherboard, bringing the total up to 4GB. I had 2GB previously and
> > things were running well with kernel 2.6.16.9 x86_64. The CPU is an
> > AM
Yes, GART_IOMMU is already turned on. Do you want me to send more
detailed debugging messages?
Presumably you're running with the GART IOMMU? If not, then turn
that on. Maybe even turn on IOMMU_DEBUG.
---
Using Tomcat but need to do more?
I tried 2.6.17-rc3 and the problem persists. I don't see any messages
about EHCI BIOS handoffs.
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your jo
On Thursday 04 May 2006 07:27, Greg KH wrote:
> Andi, you remember what fixed this the last time?
IIRC there wasn't a fix - just a conclusion that in one case it was likely
a bad interaction with SMM code. In the other case we didn't get that far.
-Andi
On Wed, May 03, 2006 at 09:52:11PM -0700, Nathan Becker wrote:
> Hi,
>
> I recently added two more memory modules to my Gigabyte K8NXP-SLI
> motherboard, bringing the total up to 4GB. I had 2GB previously and
> things were running well with kernel 2.6.16.9 x86_64. The CPU is an
> AMD 4800+ X2.
>
On Wed, 3 May 2006, Pete Zaitcev wrote:
> On Tue, 2 May 2006 10:31:14 -0700, Matthew Dharm <[EMAIL PROTECTED]> wrote:
>
> > > > So what criteria did you use to decide whether to set it to
> > > > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
> > >
> > > No, zero means "runtime-selec
On Tue, 2 May 2006 10:31:14 -0700, Matthew Dharm <[EMAIL PROTECTED]> wrote:
> > > So what criteria did you use to decide whether to set it to
> > > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
> >
> > No, zero means "runtime-selectable". The ub only works with 8/6/50
> > devices, so
On Wed, 3 May 2006, Glenn Maynard wrote:
> I think all I was visualizing was eg:
>
> int get_us_type(const struct us_data *us)
> {
> // flags that don't indicate that a device won't work with UB:
> int permitted_flags = US_FL_FIX_CAPACITY;
> if((us->flags & ~permitted_flags) != 0)
>
On Wed, 3 May 2006 10:45:14 -0700, Greg KH <[EMAIL PROTECTED]> wrote:
> On Wed, May 03, 2006 at 12:16:00AM -0700, Pete Zaitcev wrote:
> Should this also go into the -stable queue?
Yes, I think it meets criteria for -stable. It is a bug fix, is not
polluted with unrelated fixes, and is short (49 l
On Wed, May 03, 2006 at 12:16:00AM -0700, Pete Zaitcev wrote:
> In kernel 2.6.16, if a mounted storage device is removed, an oops happens
> because ub supplies an interface device (and kobject) to the block layer,
> but neglects to pin it. And apparently, the block layer expects its users
> to pin
On Wed, May 03, 2006 at 11:04:19AM -0400, Alan Stern wrote:
> On Tue, 2 May 2006, Glenn Maynard wrote:
>
> > > So, why won't we simply encode the knowledge about things which
> > > are safe for ub in a monstrous if-if-if statement? I considered
> > > this, but found it a) not safe enough, b) clums
On Tue, 2 May 2006, Glenn Maynard wrote:
> > So, why won't we simply encode the knowledge about things which
> > are safe for ub in a monstrous if-if-if statement? I considered
> > this, but found it a) not safe enough, b) clumsy, c) redundant.
>
> I guess it seems more clumsy and redundant to me
On Mon, May 01, 2006 at 11:33:09PM -0700, Pete Zaitcev wrote:
> On Mon, 01 May 2006 23:00:52 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > So what criteria did you use to decide whether to set it to
> > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
>
> No, zero means "runtime
On Mon, May 01, 2006 at 11:33:09PM -0700, Pete Zaitcev wrote:
> On Mon, 01 May 2006 23:00:52 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > So what criteria did you use to decide whether to set it to
> > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
>
> No, zero means "runtime
On Sat, 29 Apr 2006, Pete Zaitcev wrote:
> Recently, I started to receive reports of various sticks which provide
> two devices. The 0c45:1060 is one such. Often, one LUN reports its type
> as a CD, while the other is a normal storage device. This has to do with
> some data protection schemes whic
Thanks Alan,
I now implemented the claim interface strategy and it seems to work
out fine. also that way /proc/bus/usb + /dev/bus/usb won't give me any
trouble (like two drivers for the same hardware etc.).
Thanks for all your help.
Regards, Andreas
On Tue, 18 Apr 2006, Andreas Jellinghaus wrote:
> hmm. ok, I moved to flock() and now several processes have the same file
> flock()#ed exclusively, i.e. that does not work either.
>
> next fcntl()?
>
> or are device files in any way special when it comes to flock(), fcntl() and
> friend? I only
hmm. ok, I moved to flock() and now several processes have the same file
flock()#ed exclusively, i.e. that does not work either.
next fcntl()?
or are device files in any way special when it comes to flock(), fcntl() and
friend? I only want to make sure that only one process is talking to some
usb
On Tue, 18 Apr 2006, Andreas Jellinghaus wrote:
> as alternative, I can use usb functions to claim the interface.
> would that also have the desired effect? it might be even better,
> as it would allow devices with several integrated components to be
> locked only on the endpoint I use, and leave
Am Dienstag, 18. April 2006 17:10 schrieb Alan Stern:
> > all of them open it with O_EXCL?
> >
> > does O_EXCL not work standalone? should I use flock or something like
> > that instead to prevent several processes accessing the same file?
> > Or are usb device file somehow special and those method
On Tue, 18 Apr 2006, Andreas Jellinghaus wrote:
> I tried once more, and this time with /dev/bus/usb only.
>
> How can there be five processes with the same file opened?
>
> [EMAIL PROTECTED]:~# lsof |grep /dev/bus/
> ifdhandle 26749 root3u CHR189,273
>
I tried once more, and this time with /dev/bus/usb only.
How can there be five processes with the same file opened?
[EMAIL PROTECTED]:~# lsof |grep /dev/bus/
ifdhandle 26749 root3u CHR189,273
51693 /dev/bus/usb/003/018
ifdhandle 26761 root3u
Phil Dibowitz wrote:
> Olivier Blondeau wrote:
>> Hi all,
>>
>>
>> I have an USB key manufactured by ATMEL and named "SND1 Storage", which
>> has a different Vendor and ProdID than the one already included one in
>> the unusual_devs.h, and who needs his own description to work has it should:
>
> O
On Sun, 16 Apr 2006, Andreas Jellinghaus wrote:
> Andreas Jellinghaus wrote:
> > openct uses
> > open(device, O_EXCL | O_RDWR);
> >
> > so, I would assume that only one process can open a device
> > like this. unfortunatly this is not true: I have two processes
> > that have the same devi
Andreas Jellinghaus wrote:
> openct uses
> open(device, O_EXCL | O_RDWR);
>
> so, I would assume that only one process can open a device
> like this. unfortunatly this is not true: I have two processes
> that have the same device opened this way.
>
> note: I used /dev/bus/usb/*/* files, n
On Thu, Apr 06, 2006 at 12:12:04AM +0200, Bernhard Rosenkraenzer wrote:
> Attempting to use a USB 2.0 CF card reader in 2.6.16 and 2.6.16-mm2 (known to
> work back in 2.4 days, unused since) results in this:
Can you enable CONFIG_USB_STORAGE_DEBUG and send the kernel log file to
the linux-usb-dev
Mauro Carvalho Chehab wrote:
> Alan,
> Em Seg, 2006-03-20 às 23:09 +0100, thomas schorpp escreveu:
>
>>Alan Stern wrote:
>>
>>>On Wed, 15 Mar 2006, Ballentine, Casey wrote:
>
>
>>what DMA problem? ive always used via chipsets with usb. now the 8237.
>
>
>>the via pci-busmaster dma hangs the s
Alan,
Em Seg, 2006-03-20 às 23:09 +0100, thomas schorpp escreveu:
> Alan Stern wrote:
> > On Wed, 15 Mar 2006, Ballentine, Casey wrote:
> what DMA problem? ive always used via chipsets with usb. now the 8237.
> the via pci-busmaster dma hangs the system?
No. it is PCI to PCI transfers ocurring w
Alan Stern wrote:
> On Wed, 15 Mar 2006, Ballentine, Casey wrote:
>
>
>>Mauro,
>>
>>I would bet we could add the vt8235 to the list of broken chipsets
>>as well, if it's not already there. My company has completely
>>disabled DMA in the 2.6.13.4 kernel we're running on an
>>EPIA PD-1 boar
On Fri, Mar 17, 2006 at 09:59:44AM -0600, Ballentine, Casey wrote:
> Attached please find the output of "lspci -vvxxx" using the released 1.05
> BIOS and the 1.05 test BIOS on a VIA EPIA PD-1 mainboard (CLE266
> northbridge and vt8235 southbridge). Hopefully this will shed some light on
> what
Title: RE: [usb-storage] Re: [v4l-dvb-maintainer] 2.6.16-rc: saa7134 + u sb-storage = freeze
Attached please find the output of "lspci -vvxxx" using the released 1.05 BIOS and the 1.05 test BIOS on a VIA EPIA PD-1 mainboard (CLE266 northbridge and vt8235 southbridge). Hopefully this will
On Thu, Mar 16, 2006 at 04:55:11PM -0300, Mauro Carvalho Chehab wrote:
> Em Qua, 2006-03-15 às 18:44 -0500, Alan Cox escreveu:
> > On Wed, Mar 15, 2006 at 03:24:40PM -0600, Ballentine, Casey wrote:
> > > I would bet we could add the vt8235 to the list of broken chipsets
> > > as well, if it's not
Em Qua, 2006-03-15 às 18:44 -0500, Alan Cox escreveu:
> On Wed, Mar 15, 2006 at 03:24:40PM -0600, Ballentine, Casey wrote:
> > I would bet we could add the vt8235 to the list of broken chipsets
> > as well, if it's not already there. My company has completely
>
> "Works for me" 8)
On overlay mo
On Wed, 15 Mar 2006, Ballentine, Casey wrote:
> Mauro,
>
> I would bet we could add the vt8235 to the list of broken chipsets
> as well, if it's not already there. My company has completely
> disabled DMA in the 2.6.13.4 kernel we're running on an
> EPIA PD-1 board due to lockupslike thes
On Wed, Mar 15, 2006 at 06:44:21PM -0500, Alan Cox wrote:
> On Wed, Mar 15, 2006 at 03:24:40PM -0600, Ballentine, Casey wrote:
> > I would bet we could add the vt8235 to the list of broken chipsets
> > as well, if it's not already there. My company has completely
>
> "Works for me" 8)
>
> A lo
On Wed, Mar 15, 2006 at 03:24:40PM -0600, Ballentine, Casey wrote:
> I would bet we could add the vt8235 to the list of broken chipsets
> as well, if it's not already there. My company has completely
"Works for me" 8)
A lot of this is BIOS dependant and if we can isolate cases where one
BIOS w
On Thu, 9 Mar 2006, Mukund JB. wrote:
> Dear Linux USB Devels,
>
> I have studied the USB Specifications document till the chapter 5 i.e
> USB data flow model and bit and pieces of rest of the Spec.
>
> Being a novice to USB protocol, I have a set of few queries. Please help
> me clear those.
>
On Wed, 8 Mar 2006, Jean-Philippe Mengual wrote:
> Hi,
> If my device is unplugged, :00:11.4 has stat1 and stat2 at 0480.
> When my device is plugged, stat1=0490, stat2=0480.
> If you tell me that the dmesg maens the same thing than the previous, maybe
> I have the answer. But if there're new
Hi,
If my device is unplugged, :00:11.4 has stat1 and stat2 at 0480.
When my device is plugged, stat1=0490, stat2=0480.
If you tell me that the dmesg maens the same thing than the previous, maybe
I have the answer. But if there're new ideas, don't hesit.
I think, if really kernel isn't responsi
On Wed, 8 Mar 2006, Jean-Philippe Mengual wrote:
> Hi,
> I didn't have the time to buy a controller, but I tried to build 2.6.15.6.
> cat :00:11.4 (debug file) says:
> Root-hub state: auto-stopped
> HC status
> usbcmd= 0048 Maxp32 CF EGSM
> usbstat = 0020 HCHalted
> us
Hi,
I didn't have the time to buy a controller, but I tried to build 2.6.15.6. cat
:00:11.4 (debug file) says:
Root-hub state: auto-stopped
HC status
usbcmd= 0048 Maxp32 CF EGSM
usbstat = 0020 HCHalted
usbint= 0002
usbfrnum = (0)000
flbaseadd = 0133d000
> > This is total garbage, Phil. Who sent you this? Roman?
> > Look, same card (plugged into SDDR-31 and a CF-2-PCMCIA adapter):
>
> What makes you think it's garbage?
Yep, I sent this, and I also wonder why it should be gargabe ;)
No matter what card I plug in, I never can read the last sector
On Sun, 5 Mar 2006, Pete Zaitcev wrote:
> On Sun, 05 Mar 2006 21:36:51 -0800, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > The following adds an unusual_devs entry for the SanDisk ImageMate
> > CompactFlash USB.
>
> > +UNUSUAL_DEV( 0x0781, 0x0002, 0x0009, 0x0009,
> > + "SanDisk Corp
On Monday 13 February 2006 1:30 am, jinzhucheng wrote:
> David:
> I find usb otg code in linux-2.6.12/omap-udc.c, Can you tell me if you
> test otg function for omap platform using omap-udc?
Hm, this landed in my SPAM box, sorry for the delayed response...
It was last tested on 2.6.10 at some len
On Thu, Feb 23, 2006 at 10:22:55AM -0800, Pete Zaitcev wrote:
> This is a 2.4 question with a patch. I am having a deja-vu about it.
> Please look at this and let me know if it prompts any associations:
>
> It feels vaguely as if we discussed this, but I cannot find anything.
About 3 years ago we
Dear Alan,
I find nothing in the mail content. Can you please resent the mail.
Regards,
Mukund Jampala
From: Alan Stern [mailto:[EMAIL PROTECTED]
Sent: Friday, February 17, 2006 9:41 PM
To: Mukund JB.
Cc: Randy.Dunlap; [EMAIL PROTECTED];
[EMAIL PROTECT
On Wed, 15 Feb 2006, Christian Iversen wrote:
> On Wednesday 15 February 2006 17:58, Alan Stern wrote:
> > This confirms that your hardware is physically broken; it's not a software
> > problem.
> >
> > There are three UHCI controllers, one per file above, each with two ports.
> > The port statuse
On Wednesday 15 February 2006 17:58, Alan Stern wrote:
> This confirms that your hardware is physically broken; it's not a software
> problem.
>
> There are three UHCI controllers, one per file above, each with two ports.
> The port statuses are given in the lines marked "stat1" and "stat2". It
>
1 - 100 of 1046 matches
Mail list logo
