On Sun, 2008-02-24 at 21:18 -0800, Greg KH wrote:
> I have no problem exporting a simple sysfs attribute showing if the
> device is either CDMA or GSDM. I would think with that, HAL would not
> need to keep any kind of tables at all, and then the device info only
> has to stay in one place.
This
On Mon, Feb 25, 2008 at 03:07:05AM -0500, David Zeuthen wrote:
>
> On Sun, 2008-02-24 at 21:18 -0800, Greg KH wrote:
> > I have no problem exporting a simple sysfs attribute showing if the
> > device is either CDMA or GSDM. I would think with that, HAL would not
> > need to keep any kind of table
On Thursday 21 February 2008, Alan Stern wrote:
> > = CUT HERE
> > Modify EHCI irq handling on the theory that at least some of the
> > "lost" IRQs are caused by goofage between multiple lowlevel IRQ
> > acking mechanisms: try rescanning before we exit the handler, in
> > case the EHCI-int
From: Lei Ming <[EMAIL PROTECTED]>
update the comment for the removed "driver" field and being
out-of-order of @cur_altsetting and @num_altsetting.
Signed-off-by: Lei Ming <[EMAIL PROTECTED]>
---
include/linux/usb.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
mode change 100
> Well, if your devices are quite "accepting" and use standard "serial"
> lines, anything should do.
> But some special uses (for example microcontroller programmers) might
> take a LONG time (in my case, more than 3 minutes to program a PIC) to
> do the same thing a real serial port did in a real
Em Friday 22 February 2008 17:33:10 Alan Stern escreveu:
> On Thu, 21 Feb 2008, Herton Ronaldo Krzesinski wrote:
>
> > So the child branch is taken and USB_PERSIST && child->persist_enabled
> > evaluates as true. Also udev->reset_resume is enabled. The problem here
> > is inside usb_reset_device.
On Mon, 25 Feb 2008, Herton Ronaldo Krzesinski wrote:
> Hi Alan, I had some delay as only could access the hardware today. Your patch
> helped without a doubt, thanks a lot, s2ram is working ok now, here is the
> complete log:
Thanks for testing. Here is an updated version of that patch. This i
Em Monday 25 February 2008 12:10:13 Alan Stern escreveu:
> On Mon, 25 Feb 2008, Herton Ronaldo Krzesinski wrote:
>
> > Hi Alan, I had some delay as only could access the hardware today. Your
> > patch
> > helped without a doubt, thanks a lot, s2ram is working ok now, here is the
> > complete log:
On Mon, 25 Feb 2008, Jan Gutter wrote:
> Hi, I have a Cooler Master X-Craft hard drive enclosure with
> USB ID ed06:8000. (Manufacturer ID according to lsusb is DATAST0R)
>
> I've had no problems in using the drive on 2.6.23, but on vanilla 2.6.24
> I get a "device not accepting address" error in
This patch (as1039) updates the Kconfig entry for USB_SUSPEND. The
out-of-date reference to "power/state" is fixed, autosuspend is
mentioned, and the dependency on EXPERIMENTAL is removed.
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
This is just a documentation change; it should be applie
On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 22, 2008 at 05:30:22PM -0800, Chetan Karia wrote:
> > On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > > On Wed, Feb 20, 2008 at 10:35:48AM -0800, Chetan Karia wrote:
> > > > Hello,
> > > >
> > > > I am kernel newbie and I
On Mon, Feb 25, 2008 at 09:18:12AM -0800, Chetan Karia wrote:
> On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Fri, Feb 22, 2008 at 05:30:22PM -0800, Chetan Karia wrote:
> > > On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > > > On Wed, Feb 20, 2008 at 10:35:48AM -0800, Chetan Kari
On Mon, 2008-02-25 at 03:07 -0500, David Zeuthen wrote:
> On Sun, 2008-02-24 at 21:18 -0800, Greg KH wrote:
> > I have no problem exporting a simple sysfs attribute showing if the
> > device is either CDMA or GSDM. I would think with that, HAL would not
> > need to keep any kind of tables at all,
On Wed, 20 Feb 2008 07:57:23 +0100, Norbert Preining <[EMAIL PROTECTED]> wrote:
> > that you did, after taking care of detection and initialization.
> > Look at his dmesg in comment #44 in this:
>
> Yes, that looks very similar.
Someone reported on the bug that a firmware update exists to resolv
On 25/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2008 at 09:18:12AM -0800, Chetan Karia wrote:
> > On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > > On Fri, Feb 22, 2008 at 05:30:22PM -0800, Chetan Karia wrote:
> > > > On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
>
On Mon, 25 Feb 2008, Chetan Karia wrote:
> Alright, here is the entire situation. The sierra device has pair of
> endpoints (bulk in and bulk out) that sends the multiplexed protocols
> data packets ( two protocols data packets encapsulated in one). Lets
> call that endpoint pair as EP1. The one
On Mon, Feb 25, 2008 at 11:16:24AM -0800, Chetan Karia wrote:
> On 25/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Mon, Feb 25, 2008 at 09:18:12AM -0800, Chetan Karia wrote:
> > > On 22/02/2008, Greg KH <[EMAIL PROTECTED]> wrote:
> > > > On Fri, Feb 22, 2008 at 05:30:22PM -0800, Chetan Kari
On Mon, Feb 25, 2008 at 01:32:04PM -0500, Dan Williams wrote:
> On Mon, 2008-02-25 at 03:07 -0500, David Zeuthen wrote:
> > On Sun, 2008-02-24 at 21:18 -0800, Greg KH wrote:
> > > I have no problem exporting a simple sysfs attribute showing if the
> > > device is either CDMA or GSDM. I would think
On Mon, Feb 25, 2008 at 08:18:57PM +0100, Marcel Holtmann wrote:
> Hi Dan,
>
> > > > I have no problem exporting a simple sysfs attribute showing if the
> > > > device is either CDMA or GSDM. I would think with that, HAL would not
> > > > need to keep any kind of tables at all, and then the devic
Hi Dan,
> > > I have no problem exporting a simple sysfs attribute showing if the
> > > device is either CDMA or GSDM. I would think with that, HAL would not
> > > need to keep any kind of tables at all, and then the device info only
> > > has to stay in one place.
> >
> > This would be ideal. I
Hi Greg,
> > > > > I have no problem exporting a simple sysfs attribute showing if the
> > > > > device is either CDMA or GSDM. I would think with that, HAL would not
> > > > > need to keep any kind of tables at all, and then the device info only
> > > > > has to stay in one place.
> > > >
> > >
Hi Greg,
> > > > I have no problem exporting a simple sysfs attribute showing if the
> > > > device is either CDMA or GSDM. I would think with that, HAL would not
> > > > need to keep any kind of tables at all, and then the device info only
> > > > has to stay in one place.
> > >
> > > This woul
On Mon, 2008-02-25 at 11:38 -0800, Greg KH wrote:
> On Mon, Feb 25, 2008 at 01:32:04PM -0500, Dan Williams wrote:
> > On Mon, 2008-02-25 at 03:07 -0500, David Zeuthen wrote:
> > > On Sun, 2008-02-24 at 21:18 -0800, Greg KH wrote:
> > > > I have no problem exporting a simple sysfs attribute showing
Currently pxa2xx_udc spits this warning:
WARNING: at arch/arm/mach-pxa/clock.c:86 clk_disable+0x48/0xb0()
Modules linked in:
[] (dump_stack+0x0/0x14) from []
(warn_on_slowpath+0x4c/0x60)
[] (warn_on_slowpath+0x0/0x60) from []
(clk_disable+0x48/0xb0)
r6:c02162fc r5:c02178f0 r4:f260
[] (clk_d
On Sat, Feb 23, 2008 at 07:54:36PM -0800, David Brownell wrote:
> > When I suspend-to-RAM my HP nx6325 laptop with no device connected to
> > the OHCI port, the port will not be active after resuming.
>
> So I'd think any problem is related to the EHCI linkage, and
> maybe even something that's sp
Hi,
I have got a cypress usb-ide bridge and I would like to tune or monitor
my disk with tools like hdparm, hddtemp or smartctl.
My controller support a way to send raw ATA command to the disk with
something call atacb (see
http://download.cypress.com.edgesuite.net/design_resources/datasheets/co
From: David Ludlow <[EMAIL PROTECTED]>
Add support for the mos7820/7840-based B&B USOPTL4_2/USOPTL4_4 USB/RS485
converter to mos7840.c
Signed-off-by: Dave Ludlow <[EMAIL PROTECTED]>
---
DTR needs to be set/raised to receive and clear/lowered to send, as per the
mos7840 datasheet.
--- linux-2.6.
> > The sierra device has pair of endpoints (bulk in and bulk out) that
> > sends the multiplexed protocols data packets ( two protocols data
> > packets encapsulated in one). Lets call that endpoint pair as EP1.
The
> > one of the multiplexed protocol is DM and other is command and
status.
> > EP
On Mon, Feb 25, 2008 at 03:44:19PM -0800, Kevin Lloyd wrote:
> > > The sierra device has pair of endpoints (bulk in and bulk out) that
> > > sends the multiplexed protocols data packets ( two protocols data
> > > packets encapsulated in one). Lets call that endpoint pair as EP1.
> The
> > > one of
> Then please, let us know this kind of information in the beginning,
> without me having to drag it out of you all over the course of a week
> and 9 email exchanges. Don't be vague, it doesn't help anyone out,
and
> wastes people's time.
Right, miscommunication on our part.
> > I saw that the n
On Mon, Feb 25, 2008 at 04:56:39PM -0800, Kevin Lloyd wrote:
> > > I saw that the network driver framework has the ability to register
> > > packet handlers to devices data streams via the dev_add_pack
> command, I
> > > was hoping that the usb_serial drivers might have similar
> functionality
> >
On Monday 25 February 2008, Anton Vorontsov wrote:
>
> pxa2xx_udc isn't functional without the patch below, ...
Is this not already fixed by
http://marc.info/?l=linux-usb&m=120372945519098&w=2
?
Agreed this is a must-merge for 2.6.25.
-
To unsubscribe from this list: send the line "unsubscr
Kevin Lloyd wrote:
> My thought is that
> implementing this in a userspace daemon/program requires cross-process
> communication which I feel is a bit more complex (or is there a standard
> way for a userspace program to output to a virtual serial port to obtain
> the same net effect).
Perhaps pty
Hi ,
I am new to Device driver. I am developing a USB device driver
in LInux Platform for a host to host communication. Do you have any
documents which tells how to do USB host to host commmunication or a
driver code for the same. Please help me in this issue.
-
To unsubscribe from this list:
Hi:
Do you mean host to hub or really host to host?
According usb spec, no matter ehci or usb2.0, if one plays the role as host,
another one have the responsibility to receive different schedules,
Asynchronous and period, and this will make this one plays the role as
device.
It seems unreasonable i
On Monday 25 February 2008, krishna prasath wrote:
> Hi ,
>
> I am new to Device driver. I am developing a USB device driver
> in LInux Platform for a host to host communication. Do you have any
> documents which tells how to do USB host to host commmunication or a
> driver code for the same.
36 matches
Mail list logo
