I have an XXS1500 (from myCable.de) based on the
Au1500 MIPS. I am trying to make a SoundBlaster Live!
External USB card working.
Regardless of whether I use the OSS or ALSA drivers, I
get the same corrupted output: A high-frequency and
noise alternating in frequency. Always the same
pattern when
Hello,
The normal kexec boot was not successful on power 5 system. Based on
my initial look, this driver has ohci_reboot notifier, but not registered.
--- linux-2.6.12/drivers/usb/host/ohci-mem.c.orig 2005-07-08
18:11:49.0 -0700
+++ linux-2.6.12/drivers/usb/host/ohci-mem.c
Hi again,
remember me with the USB memory problems?
Anyway I studied a little of the USB specs and have a question:
All the problems seems to occur after a report back from the
USB controller with the cc register set at 6. This means that
the controller detected a PID check error. If I read the
On Fri, 2004-10-08 at 02:57, Christoph Torens wrote:
> Hi,
>
> On Mon, 04 Oct 2004 15:10:47 +0100, Ian Campbell <[EMAIL PROTECTED]>
> wrote:
>
> > Hi Lothar,
> >
> > Early in September you were working on a driver for the isp1362 based
> > upon your work with the ohci-emu/sl811 stuff. I'm just
On Fri, 2004-10-08 at 00:57, Christoph Torens wrote:
> > I have a PXA255 platform with an ISP1161 on it and am interested in
> > helping out testing, debugging etc.
>
> May I ask what a driver for isp1362 has to do with a isp116x chip?
As I understand it the isp1362 is just a isp116x core + one
Hi,
On Mon, 04 Oct 2004 15:10:47 +0100, Ian Campbell <[EMAIL PROTECTED]>
wrote:
Hi Lothar,
Early in September you were working on a driver for the isp1362 based
upon your work with the ohci-emu/sl811 stuff. I'm just wondering what
the current status of this is. Do you have a webpage with patches
Dimitris Lampridis writes:
> Hi Lothar (again),
>
> I'm missing the ohci-pci-regs.h file. Why is that?
> If i get it right it ought to be ohci.h renamed and with the read/write
> functions also declared. But I don't have the file and although your
> patch adds the line ... #include "ohci-pci-regs.
Hi Lothar (again),
I'm missing the ohci-pci-regs.h file. Why is that?
If i get it right it ought to be ohci.h renamed and with the read/write
functions also declared. But I don't have the file and although your
patch adds the line ... #include "ohci-pci-regs.h" ... it never creates
the file itself
Hi Lothar,
Early in September you were working on a driver for the isp1362 based
upon your work with the ohci-emu/sl811 stuff. I'm just wondering what
the current status of this is. Do you have a webpage with patches or
anything like that?
I have a PXA255 platform with an ISP1161 on it and am int
Hi,
On Tue, 14 Sep 2004, Lothar Wassmann wrote:
> I would like to keep the code as general as possible, so everything
> what's platform or chip dependent should be clearly separated from the
> generic stuff. For this it will be very helpful to see what has to be
> done different on different hard
Hi Olav,
> Do you accept patches for 1160-specific additions for 1362
> code? Or should I keep my changes as a separate patch for
> now?
>
Yes. No. ;)
I would like to keep the code as general as possible, so everything
what's platform or chip dependent should be clearly separated from the
generic
Hi Lothar,
Do you accept patches for 1160-specific additions for 1362
code? Or should I keep my changes as a separate patch for
now?
It would be also great to hear, what are your plans about
the rest of the 1362 code (on top of ohci-1362.h). This usb
stuff is really new to me and I feel it would
--- Lothar Wassmann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Michael Moedt writes:
> > Hi guys.
> >
> > I've been following your recent posts on linux-usb-devel.
> > I am also working with the ISP1362 chip, and I'm at the
> > point where I'd like to either port an existing 2.4 driver
> > to 2.6 or
Hi,
Michael Moedt writes:
> Hi guys.
>
> I've been following your recent posts on linux-usb-devel. I am also
> working with the ISP1362 chip, and I'm at the point where I'd like to
> either port an existing 2.4 driver to 2.6 or do something similar to
> the SL811 driver, but for the ISP chip.
>
Hi,
Dimitris Lampridis writes:
> Yes, but from what I've seen in your code, there is a Memory I/O region
> that you ioremap to dev->data_reg and dev->addr_reg. In my case, there
> is an I/O port (let's say for example address 0x200) and I must do:
> data_reg=0x200, addr_reg=data_reg + 2. Is there
Hi,
> I looked through the ohci-isp1362.h (thanks Dimitris for
> forwarding it) and compared the register layout with the one
> needed for 1160. Indeed the match is very good and it would
> suffice to add the definitions of just few registers (0x2d,
> 0x2e, and 0x41) to cover also 1160. Didn't mak
Hi guys.
I've been following your recent posts on linux-usb-devel. I am also
working with the ISP1362 chip, and I'm at the point where I'd like to
either port an existing 2.4 driver to 2.6 or do something similar to
the SL811 driver, but for the ISP chip.
I understand that you are currently in t
I looked through the ohci-isp1362.h (thanks Dimitris for
forwarding it) and compared the register layout with the one
needed for 1160. Indeed the match is very good and it would
suffice to add the definitions of just few registers (0x2d,
0x2e, and 0x41) to cover also 1160. Didn't make bit
comparis
On Fri, 2004-09-10 at 16:56, Lothar Wassmann wrote:
> > And a few more questions to be able to understand what is left to be
> > done to port the ISP1160 to your driver style:
> > 1) your SL811 is memory-mapped? This is my main problem in immitating
> >
> No. The SL811 has the same interface as the
On Mon, 2004-09-13 at 09:59, Olav Kongas wrote:
> Hi Lothar,
>
> On Sat, 11 Sep 2004, Dimitris Lampridis wrote:
>
> > On Fri, 2004-09-10 at 16:56, Lothar Wassmann wrote:
> > > No. The device could be used as a slave DMA device, but:
> > > 1) in our hardware the data register is located on a non
Hi Lothar,
On Sat, 11 Sep 2004, Dimitris Lampridis wrote:
> On Fri, 2004-09-10 at 16:56, Lothar Wassmann wrote:
> > No. The device could be used as a slave DMA device, but:
> > 1) in our hardware the data register is located on a non-DMAable
> > address (PXA DMA addresses must be aligned t
On Fri, 2004-09-10 at 16:56, Lothar Wassmann wrote:
> No. The SL811 has the same interface as the ISP1160 with an
> address/data register pair through which all internal registers are
> accessed.
>
Very good news indeed! Our cases are very similar.
> That's the simplest problem. With the macros f
On Wed, 2004-09-08 at 00:17, Lothar Wassmann wrote:
> Hi,
>
> here is a kernel [2.6.8.1] patch, that converts the SL811HS chip into
> an (more or less) OHCI compatible host controller. It has been
> developed and tested on a PXA255 platform, but should be easily
> adoptable to other platforms as w
On Thursday 09 September 2004 6:17 am, Lothar Wassmann wrote:
> Hi David,
>
> David Brownell writes:
> > That's an interesting idea, though I can imagine some chips
> > might not fit very smoothly into an OHCI-shaped hole ... :)
> >
> That's right, but OHCI offers a very stable framework for the
Hi David,
David Brownell writes:
> That's an interesting idea, though I can imagine some chips
> might not fit very smoothly into an OHCI-shaped hole ... :)
>
That's right, but OHCI offers a very stable framework for the whole
hardware independent stuff.
> Have you run this through all the "usbt
On Tuesday 07 September 2004 2:17 pm, Lothar Wassmann wrote:
> Hi,
>
> here is a kernel [2.6.8.1] patch, that converts the SL811HS chip into
> an (more or less) OHCI compatible host controller. It has been
> developed and tested on a PXA255 platform, but should be easily
> adoptable to other platf
Hi,
here is a kernel [2.6.8.1] patch, that converts the SL811HS chip into
an (more or less) OHCI compatible host controller. It has been
developed and tested on a PXA255 platform, but should be easily
adoptable to other platforms as well. And maybe serve as a base for
the adaptation of other non-O
Ian Molton wrote:
Hi.
Hi back ... your linewrap setting is broken, please
force line ends at the 72-character column or so.
is there a way to provoke interrupts from an OHCI chiip? I need to be able to generate interrupts reliably so that I can work out how to set up the chips interrupt masking /
Hi.
Im attempting to get the USB function on the TC6393XB (Toshiba multi-io chip) working.
This chip is used in their PDAs, including the e740, e750, and e800.
I have register documentation for the chip but it is very sparse, however I can bring
up the USB and have OHCI registers in memory whic
Hi Joshua,
Try reading the subject you supplied... ;-) BTW, Dave wasn't
trying to move the blame elsewhere, just trying to tell you that when he
gets the traceback he may tell you to seek help elsewhere.
regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> It's not very useful unless you include "ksymoops" output... can
> you get that, and resend along with kernel information (like the
> version etc). It'd also be good to have "objdump -dr" output
> for the relevant module, to help track down the prob
Joshua Wise wrote:
Here is the Oops log dumped to the display right before the system locks up:
It's not very useful unless you include "ksymoops" output... can
you get that, and resend along with kernel information (like the
version etc). It'd also be good to have "objdump -dr" output
for the rel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm not certain if this is the right place to report this, but I am developing
a USB client driver for the iPAQ's opensource bootldr using the ipaq.c host
driver, and have found that if the device is removed while an URB is being
sent, the
Hi All,
I tried adding the ohci host controller driver into the 2.4.4-rmk3-np1
kernel (on a StrongARM 1100/SA based system) but received the following
error during compile time: "usb-ohci currently requires PCI-based
controllers". Has anyone developed ohci drivers for the SA? Or can
any
34 matches
Mail list logo
