Am Mittwoch, 24. Mai 2006 07:35 schrieb Xu Nakajima:
> Hello,
> I had asked this question a few days ago in
> zd1211 mailing list and did not get an answer
> and I think maybe this question is more suitable
> to this forum. So please don't regard this as
> a cross posting.
>
> zd1211 is a USB w
Hello,
I had asked this question a few days ago in
zd1211 mailing list and did not get an answer
and I think maybe this question is more suitable
to this forum. So please don't regard this as
a cross posting.
zd1211 is a USB wireless dongle which has
a linux driver.
see:
http://zd1211.ath.cx
Dear Alan,
On Die, 23 Mai 2006, Alan Stern wrote:
> It's not expected but it's also not uncommon. Although 25 times in 5.4 GB
> (how many minutes was that?) sounds like a lot.
at least 26min, the first reset was at 18:11 (syslog), the last at
18:37. Is this a normal time? I had the feeling that
On 5/18/06, Guennadi Liakhovetski <[EMAIL PROTECTED]> wrote:
Hi all,
I've experimented a bit with the hub-power switching program from NIIBE
Yutaka and I've got a couple of questions to my observations.
On Sat, 14 Jan 2006, NIIBE Yutaka wrote:
> Vlado Handziski wrote:
>> http://thread.gmane.
Oh, a quick question that's been bugging me...
I assume that intr_submit() in ehci-sched.c also handles high-speed
endpoints (not just fs/ls endpoints). If so, why does
check_intr_schedule() not only blindly always assign a cmask, but also
blindly check that cmask against TT scheduling slots? T
On Tue, 23 May 2006, Norbert Preining wrote:
> Hi all!
>
> I own an iriver H300, ie an external hard disk. When I connect it via
> usb2 to my laptop or desktop pc I often get
> usb 2-2: reset high speed USB device using ehci_hcd and address 2
> This happens often, although it does not ruin
I've independently found Dan Streetman's ehci TT scheduler patches
looking for some other ssplit scheduling rule clarifications. He
implements the part I was going to do last [schedule counting]. At
this point, I've implemented the parts he didn't (FSTN and sITD
backpointer support for frame spa
2006/5/23, Alan Stern <[EMAIL PROTECTED]>:
On Tue, 23 May 2006, Franck Bui-Huu wrote:
> ok but my point is if the US_FLIDX_URB_ACTIVE bit is still set after waiting,
> doesn't that mean that the URB doesn't complete normally ? If so we should
> call usb_unlink_urb whatever the value of "timeout".
On Tue, 23 May 2006, Franck Bui-Huu wrote:
> ok so the code can be rewritten as following:
>
>clear_bit(US_FLIDX_URB_ACTIVE, &us->flags);
>if (timeout <= 0) {
>US_DEBUGP("%s -- cancelling URB\n", !timeout ?
> "Timeout" : "Signal");
>usb_unlink_urb(u
On Tue, May 23, 2006 at 05:14:03PM +0100, Craig Shelley wrote:
> Hi,
>
> I have had a few requests to add support for the CP2103 usb serial
> converter chip to the CP2101 driver. (I suspect this will end up getting
> renamed to CP210x some time in the future)
>
> This chip has 4 general purpose i
Hi all!
I own an iriver H300, ie an external hard disk. When I connect it via
usb2 to my laptop or desktop pc I often get
usb 2-2: reset high speed USB device using ehci_hcd and address 2
This happens often, although it does not ruin the files nor creates
other problems (besides the time u
Hi,
I have had a few requests to add support for the CP2103 usb serial
converter chip to the CP2101 driver. (I suspect this will end up getting
renamed to CP210x some time in the future)
This chip has 4 general purpose input/output pins which can be used to
control additional features of the targ
>> exregion-0185 [36] ex_system_memory_space: system_memory 0
>(32 width) Address=23FDFFC0
>> exregion-0185 [36] ex_system_memory_space: system_memory 1
>(32 width) Address=23FDFFC0
>> exregion-0290 [36] ex_system_io_space_han: system_iO 1 (8
>width) Address=00B2
>>
On Tue, 23 May 2006, Franck Bui-Huu wrote:
> >>> + if (test_and_clear_bit(US_FLIDX_URB_ACTIVE, &us->flags) && timeout <=
> >>> 0) {
> >> Thinking more about it, I'm wondering it the second condition (timeout <=
> >> 0)
> >> is really needed. Do you think so ?
> >
> > The test is needed becaus
> Hi subhash,
>
> What was the PHY Chip u have used. My PHY Chip is SMSC USB3300 ,
> which has an reset pin, but is not connected to any pin, but is left
> as an input,
> We are trying to find it out. Thanks for ur timely help.
>
> Did u come across the same problem of not getting interrupts when u
Alan Stern wrote:
> On Tue, 23 May 2006, Franck Bui-Huu wrote:
>
>> Franck Bui-Huu wrote:
>>> /* wait for the completion of the URB */
>>> - wait_for_completion(&urb_done);
>>> - clear_bit(US_FLIDX_URB_ACTIVE, &us->flags);
>>> + timeout = wait_for_completion_interruptible_timeout(
>>> +
On Tue, 23 May 2006, Franck Bui-Huu wrote:
> Franck Bui-Huu wrote:
> > /* wait for the completion of the URB */
> > - wait_for_completion(&urb_done);
> > - clear_bit(US_FLIDX_URB_ACTIVE, &us->flags);
> > + timeout = wait_for_completion_interruptible_timeout(
> > + &urb_
On Tue, May 23, 2006 at 12:04:59AM +0200, Frank Gevaerts wrote:
> On Mon, May 22, 2006 at 02:44:03PM -0700, Greg KH wrote:
> > 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
> > > backp
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent.
It also uses the generic scheduler function for waiting for an
event.
Signed-off-by: Franck Bui-Huu <[EMAIL PROTECTED]>
---
well I'm probably missing someth
Sorry, that was a typo from me. Its 2.4.26 or 2.4.32 kernels.
Thanks for the feedback.
Since the panic is not recreatable, I cannot test this patch. It
looks like the only option is to patch the diff and wait & watch.
Prashanth
On 5/22/06, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
On Mon, 22 Ma
Am Dienstag, 23. Mai 2006 11:40 schrieb Franck Bui-Huu:
>
> and use completion timeout instead of. It also put the task
> in interruptible state instead of uninterruptible one while
> waiting for the completion.
1. You seem to have changed the semantics of the no timeout case. May you?
2. You don
On 5/17/06, Mauro Carvalho Chehab <[EMAIL PROTECTED]> wrote:
Hmm... It seems that those drivers are without any current maintainer.
At least, from my research, I didn't noticed any patch from a maintainer
at 2.6 git tree.
Anyway, let's copy both Dmitri and Simon.
I dunno who were the authors fo
It is same as USB driver flow.
Do u know the flow?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, May 23, 2006 5:11 PM
To: linux-usb-devel@lists.sourceforge.net
Subject: linux-usb-devel digest, Vol 1 #5630 - 11 msgs
Send
Attached is a patch for testing newly added AX88178 support. For this
attempt, I have followed the mechanisms used in the OpenBSD if_axe.c
driver instead of using the initialization code provided by ASIX
themselves. It's much simpler and seems to function, though my testing
has been extremely lim
Franck Bui-Huu wrote:
> /* wait for the completion of the URB */
> - wait_for_completion(&urb_done);
> - clear_bit(US_FLIDX_URB_ACTIVE, &us->flags);
> + timeout = wait_for_completion_interruptible_timeout(
> + &urb_done, timeout ? : MAX_SCHEDULE_TIMEOUT);
>
and use completion timeout instead of. It also put the task
in interruptible state instead of uninterruptible one while
waiting for the completion.
Signed-off-by: Franck Bui-Huu <[EMAIL PROTECTED]>
---
drivers/usb/storage/transport.c | 35 +++
1 files changed
Dave:
Thanks a lot. I still have question here : )
> 2. EEM doesn't have specific descriptor, so how could host control those
> broadcast and power filters?
What filters are you talking about? The EEM spec doesn't provide any
details about such things, so it looks to me like there aren't
27 matches
Mail list logo
