Hi
I've had problems with my Netcomm USB modem with acm 21. This patch
resolves my issues with the driver. Should something like this be
integrated into acm?
Thanks
Simon Gittins
SYMPTOMS:
When using a Netcomm Roadster II 56 USB modem with acm 0.21, the serial
state (carrier detect, DSR et
Quoting keatch <[EMAIL PROTECTED]>:
> Hello, I'm working on a driver for the WebCam Go/Go Plus under Linux.
> This driver use usbvideo to manage all the usb and v4l stuff's.
>
> I need some info's about this driver. Are there some docs about it?
No. I tried to put together some, but it never ha
Hi all,
Here's a patch for the usb stv680 (Pencam) driver against 2.5.1. The
driver was written by Kevin Sisson ([EMAIL PROTECTED]). I've
cleaned it up a bit, and applied it to my 2.5 tree for sending out with
the next round of patches (which will probably be a while as Linus is
only accepting
On Mon, Dec 17, 2001 at 01:29:19PM -0800, David Brownell wrote:
>
> Looks like what the hub driver does, and discards. I'd like to see
> exactly one solution for that in the USB subsystem, so there aren't
> a variety of conventions for such names.
I agree, patches anyone? :)
> Likewise, but i
Yes, Zip drives have unique serial numbers, so they're properly
re-identified on resume and "reconnected" to their device node. There is
some work to be done here, tho doing a suspend with a mounted fs on the
device could lead to Bad Things(tm).
Of course, windows has the same problem if you
> > > > Not true at all. If a driver knows where a device is, it can do more
> > > > things. Currently no Linux driver cares about topology, but that might
> > > > change in 2.5.
> >
> > In part because the topology info is not really available ... :)
(As in, drivers are given "devnum" pre-dig
On Mon, Dec 17, 2001 at 07:51:49PM +, Riley Williams wrote:
>
> Keeping that in mind, let's take some scenarios that are already here
> and need to be dealt with by the USB subsystem:
>
> 1. Simon's laptop has no keyboard on the body of the laptop,
> and is supplied with a separate
On Mon, Dec 17, 2001 at 12:48:50PM -0800, David Brownell wrote:
> > > Not true at all. If a driver knows where a device is, it can do more
> > > things. Currently no Linux driver cares about topology, but that might
> > > change in 2.5.
>
> In part because the topology info is not really availa
> > Not true at all. If a driver knows where a device is, it can do more
> > things. Currently no Linux driver cares about topology, but that might
> > change in 2.5.
In part because the topology info is not really available ... :)
> The new HID drivers do care and pass that info to the input
Hi Martin.
>> If we're talking USB here (and in some cases even if we're not), we
>> need to deal with more than that. Specifically, we need to be able
>> to deal with the following sequences:
> [several sequences to unplug/replug same/different device while
> suspended]
>> The first three sequ
On Mon, Dec 17, 2001 at 05:55:26PM +0100, [EMAIL PROTECTED] wrote:
> > Suspend is quite different from power-cut as devices are still allowed to
> > draw up to 0.5mA from the suspended USB (see 9.2.3, USB spec.). While
> > being enough for a pm-aware microcontroler to keep its state information
>
On Mon, Dec 17, 2001 at 12:02:06PM -0800, Greg KH wrote:
> > That deferring may not always be possible. As an example, take a system
> > in use by a friend of mine, basically a laptop with the keyboard not
> > part of the main unit, but on the end of a USB lead that has to be
> > disconnected to
> Basically, we need to guarantee that on resume, all CURRENTLY PLUGGED IN
> hardware gets initialised to a known state, and anything short of that
> is just plain buggy. This includes the case where on resume, devices are
> found plugged into different ports than on suspend.
If you assume a Linu
On Mon, Dec 17, 2001 at 07:30:32PM +, Riley Williams wrote:
> Remember, one of the basic design aims of USB was that the location a
> device is plugged in is irrelevant to the user. The Linux USB drivers
> need to be totally transparent to where a particular device is plugged
> in, otherwise
On Mon, Dec 17, 2001 at 07:30:32PM +, Riley Williams wrote:
>
> That deferring may not always be possible. As an example, take a system
> in use by a friend of mine, basically a laptop with the keyboard not
> part of the main unit, but on the end of a USB lead that has to be
> disconnected to
Hi Oliver.
>> If we're talking USB here (and in some cases even if we're not), we
>> need to deal with more than that. Specifically, we need to be able
>> to deal with the following sequences:
>>
>> => Device plugged in and initialised.
>> Machine suspended.
>> Device unplugged.
>>
> If you are only downloading firmware, I'd recommend using
> usbdevfs/usbfs. This allows userspace programs to talk to usb devices.
> See libusb for an easier interface to the devices: http://libusb.sf.net/
Or jUSB for one in Java: http://jusb.sf.net ... I'm told someone has
an implementation
From lkml:
- Forwarded message from Joseph Pingenot <[EMAIL PROTECTED]> -
Date: Mon, 17 Dec 2001 12:25:03 -0600
From: Joseph Pingenot <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: USB [Toshiba PCX1100U CableModem] panic
>From Greg KH on Monday, 17 December, 2001:
>Can you ru
On Mon, Dec 17, 2001 at 12:47:13PM -0600, [EMAIL PROTECTED] wrote:
> Hello,
>
> We have a stand-alone device with a USB I/F for downloading code to Flash
> memory. Currently the only means of downloading the Flash code is via a
> DOS program (actually running from DOS, not Windows). We are tryi
> > It's my understanding that while folk can do things like that with
> > 8051-based chips like EZ-USB FX/FX2, they usually do it with
> > bank switching. So that if the firmware isn't in ROM, they'd
> > need a boot loader that knows how to populate each of the
> > various banks of memory.
>
>
Hello,
We have a stand-alone device with a USB I/F for downloading code to Flash
memory. Currently the only means of downloading the Flash code is via a
DOS program (actually running from DOS, not Windows). We are trying to
move this to Linux to eliminate the need for DOS. A skeleton driver is
> > Nope, it's a definition. Suspend/resume involves preserving
> > state. If they didn't keep power, they couldn't keep that state,
> > and they had to (re)initialize. Just like unplug/replug.
>
> This one I don't understand - why do you claim a buspowered device
> couldn't keep state over su
> [several sequences to unplug/replug same/different device while suspended]
>
> > The first three sequences means that we can't guarantee that on resume,
> > the devices available will be identical to those on suspend. The last
> > sequence means that even if it is, we may need to do more than j
>I think that in the EU the answer is that you're safe,
>and even in the US you're likely safe even though
>an increasing number of companies want to change
>that. (Example, DMCA if the protocol protects content).
Thanks Dave / Mark, I've now got a better understanding of what to avoid and
wha
> Suspend is quite different from power-cut as devices are still allowed to
> draw up to 0.5mA from the suspended USB (see 9.2.3, USB spec.). While
> being enough for a pm-aware microcontroler to keep its state information
> (like fn-address, device-config, interface alternate setting) in the
> m
> If we're talking USB here (and in some cases even if we're not), we need
> to deal with more than that. Specifically, we need to be able to deal
> with the following sequences:
>
> ==> Device plugged in and initialised.
> Machine suspended.
> Device unplugged.
> Machine resum
Hello, I'm working on a driver for the WebCam Go/Go Plus under Linux.
This driver use usbvideo to manage all the usb and v4l stuff's.
I need some info's about this driver. Are there some docs about it?
I've some problem to detect when iso packet of null lenght are received.
I need this info beca
hi greg, list,
attached is a patch for linux usb support for ipaqs running wince
3.0
what this is:
- a linux usb driver for the compaq ipaq series of handhelds running
windows ce 3.0. currently only tested with an ipaq h3135 with a usb
autosync cable. it ought to w
On Mon, Dec 17, 2001 at 11:19:31AM +0100, Martin Diehl wrote:
> > > Well, as explained in the other posting, suspend/resume is pretty much
> > > different from unplug/replug because a suspended device is still drawing
> > > some power from the suspended USB. This way even a buspowered device can
On Mon, 17 Dec 2001, Vojtech Pavlik wrote:
> > Well, as explained in the other posting, suspend/resume is pretty much
> > different from unplug/replug because a suspended device is still drawing
> > some power from the suspended USB. This way even a buspowered device can
> > keep its state and th
On Mon, Dec 17, 2001 at 10:38:17AM +0100, Martin Diehl wrote:
> > > Nope, it's a definition. Suspend/resume involves preserving
> > > state. If they didn't keep power, they couldn't keep that state,
> > > and they had to (re)initialize. Just like unplug/replug.
> > >
> > > If you want such de
On Sun, 16 Dec 2001, Riley Williams wrote:
> If we're talking USB here (and in some cases even if we're not), we need
> to deal with more than that. Specifically, we need to be able to deal
> with the following sequences:
>
[several sequences to unplug/replug same/different device while suspended
On Fri, 14 Dec 2001, David Brownell wrote:
> > > > manage dynamic loading of different overlaid firmware
> > > > images at runtime
> > >
> > > Are there devices that really do that ?
> >
> > Yep. Right here in front of me ;-)
>
> But are there are _products_ that do this and don't bother to
I
On Sat, 15 Dec 2001, Vojtech Pavlik wrote:
> > Nope, it's a definition. Suspend/resume involves preserving
> > state. If they didn't keep power, they couldn't keep that state,
> > and they had to (re)initialize. Just like unplug/replug.
> >
> > If you want such devices to get initialized the
On Thu, 13 Dec 2001, David Brownell wrote:
> > Unfortunately they can't keep power, if the host powers down,
> > as they are buspowered. And simply call them nonresumable is an
> > excuse because you don't like the remedy which is a simple clean
> > device driver.
>
> Nope, it's a definition. S
35 matches
Mail list logo
