On Friday 26 May 2006 4:16 pm, Pavel Machek wrote:
>
> > the patch appended
> > here shows what I'm pursuing. Same calling convention, new PRETHAW message
> > that "pm-naive" drivers (most of them!) can handle just like FREEZE.
> >
> > Other than this, it affects about 20 files with
Hi!
> > It's Ok if it involves a drive change, so long as its an optional change,
> > which
> > means that it shouldn't affect the interface very much (i.e. the calling
> > convention). That's why it'd be good to augment and/or modify pm_message_t
> > to implement the changes, so we wouldn't hav
On Friday 26 May 2006 2:46 pm, Robert Wuest wrote:
>
> What seems to be missing is some callback to actually initialize the sl811hs
> device. The code is there in sl811h_start and the struct hc_driver's start
> member is initalized with sl811h_start.
That would be some variant of platform_device
On Fri, 26 May 2006, Daniel Drake wrote:
> 2.6.16 introduces USB power budgeting in the Linux kernel, and since then, a
> fair number of users have observed that some of their devices no longer work
> in
> unpowered hubs (this is not a bug, the devices claim that they need more than
> 100mA).
>
On Fri, 26 May 2006, Paul Giblock wrote:
> > Perhaps it will be good enough to limit the timing between URBs generated
> > by your driver. URBs coming from somewhere else won't be your
> > responsibility.
> >
>
> Thats exactly my plan. I'm just having trouble devising a good way to do
> this.
I am trying to get USB running on a Broadcom 1480 board with an sl811hs host
controller. The device checks out under CFE (BIOS).
I have configured my kernel and selected the sl811-hcd driver and when I boot,
I see the 'sl811: driver sl811-hcd, 19 May 2005' message.
When I do a dir /proc/bus/usb,
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
> > + /* Set brightness in backlight device */
> > + up(&pdata->bd->sem);
> > + pdata->bd->props->brightness = brightness;
> > + down(&pdata->bd->sem);
>
> Ditto. If it's attempting to synchronise against appledisplay_work() in
> some way then I'd have thought it was racy..
Heh, smells
Hi, all!
I've recently found that ftdi_sio driver could cause some problems:
* kernel panic: write much more data than device can transimt at once
and disconnect device, system hangs((
* ftdi_sio could ran out of memory write lots of data to device after
some time you'll see that in kernel log.
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
Michael Hanselmann <[EMAIL PROTECTED]> wrote:
>
> +#include
backlight_device would appear to need mutex conversion.
Then again, maybe we take backlight_device.sem recursively - I do recall
some pretty wild happenings in there.
> +static void appledisplay_work(void *private)
> +{
> + struct
On Friday 26 May 2006 05:06, David Brownell wrote:
> On Tuesday 02 May 2006 9:12 am, Patrick Mochel wrote:
> > On Thu, Apr 27, 2006 at 12:41:28PM -0700, David Brownell wrote:
> >
> > > There does seem to be agreement that the current FREEZE invocation is not
> > > sufficient. I'm looking at a sli
Perhaps it will be good enough to limit the timing between URBs generated
by your driver. URBs coming from somewhere else won't be your
responsibility.
Thats exactly my plan. I'm just having trouble devising a good way to do this.
If you want to be really clever, you can keep track of the
Hi there,
Can somebody tell me how should I begin porting the ISP116 Host
Controller Driver to the Embedded Platform. I am going to use the
PowerPC (RISC) Chip. I would like to hook up the USB Controller to the
PIO of the processor.
What I am trying to do is, having a ISP116x part on the embedde
Dear Alan!
On Fre, 26 Mai 2006, Alan Stern wrote:
> UNUSUAL_DEV( 0x1006, 0x3003, 0x0100, 0x0100,
> "iRiver",
> "H300 Series",
> US_SC_DEVICE, US_PR_DEVICE, NULL,
> US_FL_GO_SLOW ),
Ok, didn't change anything. But I have some more obervation
Hi,
I got this when disconnecting an ipaq with 2,6,17rc4.
Frank
usb 1-4.5.7: USB disconnect, address 79
[ cut here ]
kernel BUG at kernel/workqueue.c:110!
invalid opcode: [#1]
Modules linked in: uhci_hcd ohci_hcd ehci_hcd ppp_deflate zlib_deflate bsd_comp
ppp_async
now the driver acts much more sane.
Remove more log spamming from pegasus: stop talking to the device once we
see ENODEV reported. It may take a while before khubd notifies us.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Index: linux/drivers/usb/net/pegasus.c
That looks good to me, I will come up with a similar patch.
Jan
David Brownell wrote:
>On Thursday 25 May 2006 8:15 am, Jan Capek wrote:
>
>
>>Hi,
>>
>>I have come across an issue when compiling the ohci-hcd driver as module
>>when PCI and USB_OHCI_HCD_PPC_SOC are both enabled. The compilatio
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 Thursday 25 May 2006 8:15 am, Jan Capek wrote:
> Hi,
>
> I have come across an issue when compiling the ohci-hcd driver as module
> when PCI and USB_OHCI_HCD_PPC_SOC are both enabled. The compilation of USB
> subsystem fails due to the fact that ohci-hcd.c has some of its
> components(ohci-p
There is currently no FSTN support, just placeholder code in ehci-sched.c.
I have implemented FSTN support (along with sITD backpointer support)
and am in the process of implementing a new TT scheduler as well. My
work is currently against 2.6.17-rc3. Enough has happened in the USB
code that my
On Friday 26 May 2006 5:16 am, Milan Svoboda wrote:
>
> Feedback and comments are highly appreciated.
To repeat the feedback I sent when you first posted these on the ARM list:
(a) Split out the ARM platform patches from the USB patches.
Your patches #2 and #3 still mix the two up.
(b) i
On Friday 26 May 2006 5:16 am, Milan Svoboda wrote:
> From: Milan Svoboda <[EMAIL PROTECTED]>
>
> Add support for full speed only udc controllers.
> Current status is that build fails if udc supports
> only LOW/FULL speed.
As I explained the first time you send this patch:
not needed, REJECTED.
On Friday 26 May 2006 5:17 am, Milan Svoboda wrote:
> From: Milan Svoboda <[EMAIL PROTECTED]>
>
> usbgadgetfs allows userspace to open as many enpoints as it
> needs. It's not good to limit number of endpoints by the udc
> driver in this case.
ACK.
On Fri, 26 May 2006, Norbert Preining wrote:
> > Your symptoms remind me a little of what used to happen with the Genesys
> > chips. Maybe the same solution will help. Do you know how to add an
> > entry for your drive into the unusual_devs.h file? It should contain the
> > US_FL_GO_SLOW fla
On Fri, 26 May 2006, Paul Giblock wrote:
> I've been working on my kernel module and everything have been coming
> along nicely. There is one issue with my device. If I send two urbs
> to the device without enough wait between the calls then the device
> doesn't respond with status messages anym
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
Hi All,
Our team is developing a USB OTG Controller driver for Linux 2.6.16.11
kernel on a board which runs on ARM Core . The driver is for ARC USB
OTG Controller.
There are three modules involved viz
Host Controller Driver
Device Contro
Hello Oliver
On Fri, May 26, 2006 at 11:29:14AM +0200, Oliver Neukum wrote:
> > + char buffer[2];
> DMA on the stack. You must not do this. Allocate the buffer with kmalloc.
This and the other errors are fixed in the patch below.
Thanks,
Michael
---
diff -Nrup --exclude-from linux-exclud
From: Milan Svoboda <[EMAIL PROTECTED]>
usbgadgetfs allows userspace to open as many enpoints as it
needs. It's not good to limit number of endpoints by the udc
driver in this case.
This patch is against 2.6.17-rc5.
Signed-off-by: Milan Svoboda <[EMAIL PROTECTED]>
---
--- orig/drivers/us
From: Milan Svoboda <[EMAIL PROTECTED]>
This patch adds IXP465 into the list of known devices and
adds IXP425 and IXP465 to the list of devices that have cfr. This
is not described in the hardware documentation, but without
it driver won't work.
Workaround (#if 1) that seemed to get rid of lost
From: Milan Svoboda <[EMAIL PROTECTED]>
This patch adds platform device ixp4xx_gadget that uses pxa2xx-udc
device driver. Also pxa2xx_udc.c is updated so it can be compiled
without errors on IXP4XX architecture.
The patch is against 2.6.17-rc5.
Signed-off-by: Milan Svoboda <[EMAIL PROTECTED]>
-
From: Milan Svoboda <[EMAIL PROTECTED]>
Add support for full speed only udc controllers.
Current status is that build fails if udc supports
only LOW/FULL speed.
This patch is against 2.6.17-rc5.
Signed-off-by: Milan Svoboda <[EMAIL PROTECTED]>
---
--- orig/drivers/usb/gadget/inode.c
Hello,
following patches update pxa2xx_udc driver and ixp4xx arch depended
files. This driver will be usable on ixp4xx platform without problems.
Current state is that the pxa2xx_udc.c can't be even compiled for
the IXP4xx platform.
Patches were tested on IXDP465 and on IXDP425 and passed all t
Hi Alan!
On Don, 25 Mai 2006, Alan Stern wrote:
> Well, don't be in too big a hurry to give up. If you're having these
> problems, the chances are reasonably good that other people with similar
> hardware are too. They just don't notice or complain about it. But we
> would like the driver to wo
Am Freitag, 26. Mai 2006 11:15 schrieb Michael Hanselmann:
> +static int __init appledisplay_init(void)
> +{
> + wq = create_singlethread_workqueue("appledisplay");
> + BUG_ON(!wq);
That's not a BUG.
Regards
Oliver
Am Freitag, 26. Mai 2006 11:15 schrieb Michael Hanselmann:
> +static void appledisplay_disconnect(struct usb_interface *iface)
> +{
> + struct appledisplay *pdata = usb_get_intfdata(iface);
> +
> + if (pdata) {
> + cancel_delayed_work(&pdata->work);
> + usb_k
Am Freitag, 26. Mai 2006 11:15 schrieb Michael Hanselmann:
> + if (usb_submit_urb(pdata->urb, GFP_ATOMIC)) {
> + retval = -EIO;
GFP_KERNEL will do.
Regards
Oliver
---
All the advantages of Linux Mana
Am Freitag, 26. Mai 2006 11:15 schrieb Michael Hanselmann:
> +static int appledisplay_bl_update_status(struct backlight_device *bd)
> +{
> + struct appledisplay *pdata = class_get_devdata(&bd->class_dev);
> + char buffer[2];
> + int retval;
> +
> + buffer[0] = 0x10;
> +
This is a driver to control the brightness of an Apple Cinema Display
over USB. It updates the local brightness value if the user presses a
button on the display.
Please apply to -mm for testing if nothing major is broken.
Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
---
diff -Nrup --ex
I've been working on my kernel module and everything have been coming
along nicely. There is one issue with my device. If I send two urbs
to the device without enough wait between the calls then the device
doesn't respond with status messages anymore. Is there a kernel
mechinism available to ha
41 matches
Mail list logo
