Someone might want to look at this... presumably the bug
shows up in current code.
-- Forwarded Message --
Subject: [avrdude-dev] ser_posix.c: is select()ing for the write descriptor
useful at all?
Date: Wednesday 18 April 2007 1:36 pm
From: Joerg Wunsch <[EMAIL PROTECTED]>
To:
On Wed, 18 Apr 2007 18:08:48 +0200, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 18. April 2007 17:54 schrieb Mike Panetta:
> > Just out of curiosity, why do we want to get rid of ioctl calls?
> For a number of reasons.
> - we got burned on 32/64 issues
That's actually a reason to su
On Wed, 18 Apr 2007, John Wojnaroski wrote:
> Alan Stern wrote:
>
> >On Wed, 18 Apr 2007, John Wojnaroski wrote:
> >
> >
> >
> >>OK, so an IN transfer might look something like <22 09 0200 >
> >>
> >>
> >
> >Except that it couldn't use 0x22 in the first byte. The high-order bit
> I also agree with Alan Cox that that specific software should be found
> in, as stated, on "well known locations", and "distributed by vendors".
> It seems that we do have a few people from Huawei that can help us try
> to achieve that. I'll try to CC all of them.
Ok here's a serious suggestion
> This "small piece of source" seems be the better solution because ppl
> from Huawei stated it will work...
The small piece of code isn't even distribution shippable - consider for
example the firmware files with it - I can find no license.
If the right way to do this is with a helper app the
Quoting Rui Santos <[EMAIL PROTECTED]>:
> Greg KH wrote:
>> On Tue, Apr 17, 2007 at 03:31:55PM +0100, Alan Cox wrote:
>>
>>> On Sun, 15 Apr 2007 23:42:40 -0700
>>> Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>>>
>>>
Greg,
This patch removes the entry for the Huawei patch at the request
On Wed, Apr 18, 2007 at 01:30:14PM +0200, Jeroen Janssen wrote:
> Hello,
>
> It seems that
> http://git.kernel.org/?p=linux/kernel/git/gregkh/usb-2.6.git;a=summary
> is displaying an 'empty' repository (at least here).
That is the tree I use to push to Linus. If there is nothing that I
need to
Hi David,
> > I had a look at a few Linux drivers, but had trouble finding complete
> > datasheets for the chips. It seems the FTDI232BM support 500kb/s, but I
> > found no protocol documentation describing available RTS modes.
>
> The newer FTDI 232R series chips (vs 232B, which isn't ROHS-confor
Alan Stern wrote:
>On Wed, 18 Apr 2007, John Wojnaroski wrote:
>
>
>
>>OK, so an IN transfer might look something like <22 09 0200 >
>>
>>
>
>Except that it couldn't use 0x22 in the first byte. The high-order bit of
>that byte determines the direction. It would have to be 0xa2.
Hi David,
> > I came across a device which exposes class specific interface descriptors
> > (CS_INTERFACE) that the current Linux kernel code can't parse.
> >
> > Most USB devices describe the class specific interface data between the
> > interface descriptor and its associated endpoint descriptor
On Wed, Apr 18, 2007 at 11:23:23AM -0400, Alan Stern wrote:
> On Tue, 17 Apr 2007, Sarah Bailey wrote:
>
> > On Tue, Apr 17, 2007 at 11:50:09AM -0400, Alan Stern wrote:
> > > On Mon, 16 Apr 2007, Sarah Bailey wrote:
> > >
> > > > usbfs2 will have asynchronous support for bulk, interrupt, and
> >
On Wed, Apr 18, 2007 at 11:54:09AM -0400, Mike Panetta wrote:
> Alan Stern wrote:
> >On Tue, 17 Apr 2007, Sarah Bailey wrote:
> >
> >>
> >> To be truthful, I haven't thought out that far. I suspect that some of
> >> the functionality (like setting the device's address, changing the
> >> altsetting
Am Mittwoch, 18. April 2007 17:54 schrieb Mike Panetta:
> Just out of curiosity, why do we want to get rid of ioctl calls? They
> aren't all that bad, are they? With an ioctl call its obvious you want
> to write some structured data of some sort to a device to control it,
> with read/write its
On Tue, 17 Apr 2007, Sarah Bailey wrote:
> On Tue, Apr 17, 2007 at 11:50:09AM -0400, Alan Stern wrote:
> > On Mon, 16 Apr 2007, Sarah Bailey wrote:
> >
> > > usbfs2 will have asynchronous support for bulk, interrupt, and
> > > isochronous transfers. It will also represent USB devices as several
On Wed, 18 Apr 2007, Johannes Berg wrote:
> Hi,
>
> Here's something I just observed yesterday. At first I was blaming my
> suspend changes for powerpc since I can't make it happen without them,
> but I've gone back and forth over them and can't find the problem, so
> while I'm still not sure the
On Wed, 18 Apr 2007, Jiri Kosina wrote:
> On Wed, 18 Apr 2007, Jeroen Janssen wrote:
>
> > I noticed several recent USB SUSPEND related patches on this mailinglist
> > and I was wondering if someone could tell me what the current state of
> > USB SUSPEND is. Should USB devices be suspend 'autom
Alan Stern wrote:
> On Tue, 17 Apr 2007, Sarah Bailey wrote:
>
> >
> > To be truthful, I haven't thought out that far. I suspect that some of
> > the functionality (like setting the device's address, changing the
> > altsetting, and changing the device configuration) could be associated
> > with a
On Tue, 17 Apr 2007, David Brownell wrote:
> > All examples found in USB specification documents put the
> > CS_INTERFACE descriptors between the INTERFACE and ENDPOINT descriptors,
> > but
> > I found no mention of this being a requirement.
> >
> > The interface descriptor parsing code (usb_
On Tue, 17 Apr 2007, John Wojnaroski wrote:
> Hmm, now I'm puzzled. Does the byte order actually depict the sequence
> of the bits sent by the OS?
Yes, although the way in which the order depicts the sequence depends on
the formatting of the particular message in question.
> Is this a diffe
On Tue, 17 Apr 2007, Mark Glassberg wrote:
> On Tue, Apr 17, 2007 at 12:56:51PM -0400, Alan Stern wrote:
> > There was a fairly recent change in this area of choose_configuration(),
> > having to do with whether or not RNDIS support is present in a module vs.
> > built-in. Mark should try using
Thanks, the list was very helpful.
On Wed, 2007-02-14 at 15:02 -0800, Pete Zaitcev wrote:
> On Wed, 14 Feb 2007 15:47:16 -0700, Jeremy Roberson <[EMAIL PROTECTED]> wrote:
>
> > With the help of Dmitry, I solved the exclusive access issue that
> > required blacklisting our IPanel so, I'm going t
Am Mittwoch, 18. April 2007 13:22 schrieb Jeroen Janssen:
> Hello,
>
> I noticed several recent USB SUSPEND related patches on this
> mailinglist and I was
> wondering if someone could tell me what the current state of USB SUSPEND is.
It basically works, but is supported in few drivers.
> Also I
On Wed, 18 Apr 2007, Jeroen Janssen wrote:
> I noticed several recent USB SUSPEND related patches on this mailinglist
> and I was wondering if someone could tell me what the current state of
> USB SUSPEND is. Should USB devices be suspend 'automaticly' (by the
> kernel) when suspending to ram?
Hello,
It seems that
http://git.kernel.org/?p=linux/kernel/git/gregkh/usb-2.6.git;a=summary
is displaying an 'empty' repository (at least here).
Also it seems http://www.kernel.org/pub/scm/linux/kernel/git/gregkh/
doesn not contain usb-2.6.git (anymore)?
Can someone confirm this?
Jeroen
-
Hello,
I noticed several recent USB SUSPEND related patches on this
mailinglist and I was
wondering if someone could tell me what the current state of USB SUSPEND is.
Also I would appreciate it if someone can tell me if USB SUSPEND
should be working
in the (fc6) 2.6.19 kernel (since that is what
Greg KH wrote:
> On Tue, Apr 17, 2007 at 03:31:55PM +0100, Alan Cox wrote:
>
>> On Sun, 15 Apr 2007 23:42:40 -0700
>> Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Greg,
>>>
>>> This patch removes the entry for the Huawei patch at the request of the
>>> manufacturers and other users. S
On Wed, 2007-04-18 at 02:25 -0700, David Brownell wrote:
> On Wednesday 18 April 2007 1:43 am, Johannes Berg wrote:
> >
> > It seems to me that the timer shouldn't be scheduled when we go into
> > suspend,
>
> Right ... this would be a post-2.6.21 fix right?
I don't really know if it applies to
On Wednesday 18 April 2007 1:43 am, Johannes Berg wrote:
>
> It seems to me that the timer shouldn't be scheduled when we go into
> suspend,
Right ... this would be a post-2.6.21 fix right?
Do you know which specific line schedules that timer?
> but I'll leave the proper fix up to somebody el
Hi,
Here's something I just observed yesterday. At first I was blaming my
suspend changes for powerpc since I can't make it happen without them,
but I've gone back and forth over them and can't find the problem, so
while I'm still not sure they aren't at fault I wanted some input from
the USB side
Am Donnerstag, 5. April 2007 06:41 schrieb Shawn Bohrer:
> This patch does seem to fix the problem I described, though admittedly
> I haven't exactly figured out how you are supposed to use the ldusb
> driver. It looks like I need to first write some magic numbers to
> initialize the device before
30 matches
Mail list logo