Hi.
Thanks, guys, for this driver. I hope I can get it to work.
I've been trying to use this driver for a while. Right now, I've got
it compiled into 2.6.8.1, and the kernel runs. (I'm using the
2004-10-11 version from the KARO website) I had to make some
modifications to fit it into my archi
Alan Stern wrote:
You can probably get more information if you turn on the USB debugging
option in the kernel configuration.
Here's what happens with ehci_hcd verbose debugging enabled:
Oct 14 14:55:52 tbolt kernel: ehci_hcd 00:1d.7: GetStatus port 1 status
001000 POWER sig=se0
Oct 14 14:55
On Wed, Oct 13, 2004 at 07:57:22PM -0700, Andrew Morton wrote:
>
> Can we just kill that printk for now?
>
> Begin forwarded message:
>
> Date: Wed, 13 Oct 2004 18:03:08 -0700
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Bugme-new] [Bug 3564] New: USB Problem
>
>
> http://bugm
Hi Alan,
> > I ran across such a device not so long ago. Could you post your patch (or
> > send it to me directly) so that I could test it ?
>
> A preliminary version of the patch is available here:
>
> http://marc.theaimsgroup.com/?l=linux-usb-users&m=109717585508982&w=2
>
> It includes an extra
Hi,
Reverse engineering shouldn't be needed! :)
On Friday 15 October 2004 2:08 pm, Sven Geggus wrote:
>
> Linux fails while trying to enable the device as HID:
>
> usb 2-1: new low speed USB device using address 3
> drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint
> usbh
David Brownell wrote:
If you would, please. I just wasn't sure about the more global
ramifications of that.
Attached ... see if it behaves for you.
Yes, that fixes the reported warning messages.
Thanks,
~Randy
Fix some compi
On Fri, 2004-10-15 at 15:42, Lee Revell wrote:
> > Either way, the generic IRQ code should deal with
> > duplicates without generating an oops.
>
> Agreed, this bug should be fixed either way.
I just finished some more testing,
and the problem is just as I described.
I was able to reproduce the
Hi there,
I recently got myself an USB controlled 4-way mains socket outlet.
Unfortunately there are no Linux drivers available:(
Disassembly of the device showed me a CY7C63723 Microcontroller connected to
a i2c EEPROM and Relais conected to GPIO Ports of the Microcontroller.
Linux fails while
On Fri, 2004-10-15 at 13:36, Paul Fulghum wrote:
> Unique device names are useful for identifying
> which device instance is on a particular interrupt
> (/proc/interrupts), but other drivers beside uhci_hcd
> use a constant name so I guess that is legal :-)
>
I agree that this would be a useful e
On Friday 15 October 2004 12:19 am, Matthew Dharm wrote:
> On Thu, Oct 14, 2004 at 04:54:38PM -0700, David Brownell wrote:
> > Hi Matt,
> >
> > On Thursday 14 October 2004 3:46 pm, Matthew Dharm wrote:
> > >
> > > ...I've discovered that the EHCI controller in the AMD-8111
> > > southbridge doesn
On Thursday 14 October 2004 7:25 pm, Randy.Dunlap wrote:
> Could mark req.dma as __le32...
> >>
> >>I didn't like that suggestion (yet), other people can comment on it,
> >>though. For now I'm just adding a cast.
> >
> >
> > Changing that type for sparse sounds better to me, so it works
> >
> I've been following this discussion for a while. I'm also working
> on getting USB working on an isp1160 chip on a power pc platform.
> Since I couldn't find any official drivers for this chip, I am
> encouraged that there is some progress in this area.
Hey, I'm encouraged too.
> I've got th
On Thu, 14 Oct 2004, Roe Peterson wrote:
> Alan Stern wrote:
>
> >
> >
> >You can probably get more information if you turn on the USB debugging
> >option in the kernel configuration.
> >
> >
> Here's what happens with ehci_hcd verbose debugging enabled:
Nothing stands out. Can you try usi
Hello Everyone,
I've been following this discussion for a while. I'm also working on
getting USB working on an isp1160 chip on a power pc platform. Since I
couldn't find any official drivers for this chip, I am encouraged that there
is some progress in this area. So I went ahead and downloaded L
Greg:
Here's another USB mass storage device that incorrectly reports the total
number of disk blocks. Please apply.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/storage/unusual_devs.h 1.152 vs edited =
--- 1.152/drivers/usb/storage/unusual_devs.h2004-09
On Fri, 2004-10-15 at 12:21, Alan Stern wrote:
> As I understand it, the description field is just a human-readable string
> that indicates what sort of device the hcd is. It doesn't need to be
> unique. In fact, the kerneldoc for request_irq() (without the updates)
> says that the dev_id value
On Fri, 15 Oct 2004, Paul Fulghum wrote:
> There was a question in my mind about the hcd->description field.
> Should it be unique for each device instance instead
> of uniform for all device instances on a driver?
As I understand it, the description field is just a human-readable string
that ind
On Friday 15 October 2004 9:48 am, Paul Fulghum wrote:
> On Fri, 2004-10-15 at 11:18, Alan Stern wrote:
> > Your explanation sounds entirely reasonable to me. Can you pass it on to
> > the people responsible for the generic-irq subsystem?
>
> I CCd Ingo Molnar, who appears to be the originator
>
On Fri, 2004-10-15 at 11:18, Alan Stern wrote:
> Your explanation sounds entirely reasonable to me. Can you pass it on to
> the people responsible for the generic-irq subsystem?
I CCd Ingo Molnar, who appears to be the originator
of these patches.
There was a question in my mind about the hcd->
On Fri, 15 Oct 2004, Paul Fulghum wrote:
> This looks like it is related to the generic-irq-subsystem patches.
> Specifically, adding and removing proc entries for each interrupt.
>
> Laurent's configuration has two controllers sharing the same interrupt.
> The hcd->description for both controlle
On Fri, 15 Oct 2004, Steve Krulewitz wrote:
> Alan --
>
> Alan Stern wrote:
> > On Sat, 9 Oct 2004, Steve Krulewitz wrote:
> > This looks like a bug in the iPod. After transferring 312 64-byte packets
> > it tried to send something longer than 64 bytes. Probably 512 bytes, for
> > some reason
Alexander:
Try using this patch instead of the one you had from before. If this
works it can go into the regular kernel.
Alan Stern
= drivers/usb/host/uhci-hcd.c 1.134 vs edited =
--- 1.134/drivers/usb/host/uhci-hcd.c 2004-09-30 13:58:40 -04:00
+++ edited/drivers/usb/host/uhci-hcd.c
On Thu, 2004-10-14 at 18:21, Laurent Riffard wrote:
> Alan Stern wrote:
> > Yes, try that. At least if the problem still occurs, it will be
> > easier to track down.
> >
> > Alan Stern
> >
>
> I just tried kernel 2.6.9-rc4 : it woks fine, there is no oops when
> I rmmod uhci_hcd.
Alan:
This
Alan --
Alan Stern wrote:
On Sat, 9 Oct 2004, Steve Krulewitz wrote:
This looks like a bug in the iPod. After transferring 312 64-byte packets
it tried to send something longer than 64 bytes. Probably 512 bytes, for
some reason thinking it was running at high speed rather than full speed.
I p
karsten wiese wrote:
UHCI_NUMFRAMES will never change, it is a standard.
Ok, then
I'll recheck with gcc 3.4 of fc3. I guess it'll stay the
same. Anyhow this is interrupt level, time critical code so
I think the patch is the right way to go.
I just checked this code:
unsigned int test(void)
{
retu
--- Paulo Marques <[EMAIL PROTECTED]> schrieb:
> karsten wiese wrote:
> > Ok, thats not much, but it dosn't harm either.
> > Erm, at least as long as UHCI_NUMFRAMES is a power of
> 2
> > ;-)
>
> > - framenum %= UHCI_NUMFRAMES;
> > + framenum &= (UHCI_NUMFRAMES - 1);
>
> This seems like it
Hi all,
I am currently trying to implement the USB host controller for the MPC8270. As you
would be aware, the Host controller on this chip is neither UHCI nor OHCI compliant. I
am trying to follow up on Brad Parker's architecture for my development.
(you can find Brad's 8xx USB work at: http:/
Hi all,
I am currently trying to implement the USB host controller for the MPC8270. As you
would be aware, the Host controller on this chip is neither UHCI nor OHCI compliant. I
am trying to follow up on Brad Parker's architecture for my development.
(you can find Brad's 8xx USB work at: http:/
karsten wiese wrote:
Ok, thats not much, but it dosn't harm either.
Erm, at least as long as UHCI_NUMFRAMES is a power of 2
;-)
- framenum %= UHCI_NUMFRAMES;
+ framenum &= (UHCI_NUMFRAMES - 1);
This seems like it should really be handled by the compiler... Did you
try a more recent g
Hi!
I have posted this yesterday to the lkml, but
I think linux-usb-devel is a better place to discuss.
I have a problem with my USB keyboard.
It seems that the keyboard is recognized somehow, but it's not working at
the end.
I have tested this with Kernel 2.6.9-rc4, 2.6.8.1 and 2.6.4 with the s
On Thu, Oct 14, 2004 at 04:54:38PM -0700, David Brownell wrote:
> Hi Matt,
>
> On Thursday 14 October 2004 3:46 pm, Matthew Dharm wrote:
> >
> > In my 'day job', I've discovered that the EHCI controller in the AMD-8111
> > southbridge doesn't work. As in, AMD published errata says it doesn't
> >
Hi. This is the qmail-send program at beta.sigadel.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)
--- Below this line
32 matches
Mail list logo
