Hi there!
This mail is mainly directed to the couple of guys developing a driver
for the isp1362 or isp1162 philips chips. I am one of them now :)
I am a colleague of torsten and we both are desperately (:-)) trying the
here and private exchanged patches vor the mentioned chips into a
2.6.10-rc2
What I forgot to ask, on what processors are you using the isp1362 or
1161 HCs? We try to get it running on a Motorola i.MX processor.
I wonder, if this platform setup is reasonable or breaks stuff:
void ohci_isp1362_hw_reset(int id, int set)
{
}
static struct ohci_chip_info ohci_1362_data = {
Am 2004-11-29 16:19 +0100 schrieb Konstantin Kletschke:
> This mail is mainly directed to the couple of guys developing a driver
> for the isp1362 or isp1162 philips chips. I am one of them now :)
Well its a mess. I found some bugs today, but obviously not all...
I will be very happy if s
Am 2004-11-30 09:08 +0200 schrieb Olav Kongas:
> ISTL: 2 * 0 , because the driver currently does not support
> iso transfers
Argh! I wondered, why somebody (you?) put 0 into the two variables :)
> > isp1362-ohci isp1362-ohci0: INTL: 4 * 64: 288
>
> INTL: 0 * whatever , because 116x does n
Am 2004-11-30 09:53 +0200 schrieb Olav Kongas:
> Just wondering, are you using software reset or no reset at
> all?
I _hope_ I use software reset. Definately no hardware reset.
The isp1362 initializing functions say they are resetting the chip, but
I will take a closer look...
> >
Am 2004-11-30 11:51 +0200 schrieb Olav Kongas:
> Then you are using no reset at all.
Well, is this general a show stopper? In my opinion that should
not break the state when powered up, but...
> If you don't use dma, you can lie to the initialization code
> that all low 4GB memory is dma-able.
Am 2004-11-30 08:39 -0800 schrieb Michael:
> > there are three locations where this Value
> > gets written in the driver, and none works? :)
> >
>
> I had this problem at one point as well. When I integrated
> Lothar's latest patch, the problem was solved. Before that, I just
> added it to one
Please, I would appreciate if somebody takes a look at:
http://www.ludenkalle.de/usb/oops2.txt
Is
alloc_ptd: Trying to find PTD for 0 byte of type 0
alloc_ptd: Set bit 0001 in bufmap @ c02d494c: 0001
buf_curlen(old) = 0
buf_curlen(new) = 8, xfer_si
Am 2004-11-30 10:02 -0400 schrieb Philipp Schmid:
> HCISTL0PORT [40]: 2040
> would be the issue. Instead, it almost looks more like you are reading back
> the address register somehow, as all 32 bit data regs contain their address
> value.
Ah! Now I see that too! WTF? How can this sh*** com
Am 2004-11-30 19:29 +0100 schrieb Konstantin Kletschke:
>
> Please, I would appreciate if somebody takes a look at:
>
> http://www.ludenkalle.de/usb/oops2.txt
We fixed a couple of typos and errors introducing your patches into
2.6.10-rc2 and finally the isp1161a1 enumerates
Hi again :)
Now we are trying to get some usb device to do anything useful.
Of course I expect to trigger bugs, which are left in the code :)
This is, when trying to start wlan:
prism2usb_init: prism2_usb.o: 0.2.1-pre23 Loaded
prism2usb_init: dev_info is: prism2_usb
usbcore: registered
Am 2004-12-01 15:15 +0200 schrieb Dimitris Lampridis:
> Hey guys,
> how did you manage to overcome the problem with the frame interval
> register? I'm getting too only FrameInterval and no FSMPS...
What is your problem with the frame interval register actual exactly?
IIRC I set it to 0x27782edf in
Am 2004-12-02 11:15 +0200 schrieb Olav Kongas:
> In your case, it most likely corresponds to the STATUS stage
> of the control transfer.
So you mean it is an absolutely normal thing happening there?
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
Am 2004-12-02 15:15 +0200 schrieb Dimitris Lampridis:
> > Hrm.. It must be getting overwritten.
> No it is not! The register gets written only once during hc_start() of
> ohci-hcd.c when periodic_reinit() is called. And although the value of
> 0x27782edf is sent to the data port, the register sho
Lothar schrieb:
> >with Line 417 being
> >
> >WARN_ON((!(__isp1362_read_reg16(dev, HCuPINT) & HCuPINT_ISP116x_AIIEOT)));
> ALLEOT is set when the amount of data programmed in the XFERCOUNT
> register has been transferred to/from the chip buffer. If it's not set
> at the end of the the read/write_
c 2004 15:28:43 +0100
From: Torsten Koschorrek <[EMAIL PROTECTED]>
Organization: synertronixx GmbH
To: Konstantin Kletschke <[EMAIL PROTECTED]>
Subject: Re: [linux-usb-devel] ISP116x / 1362 driver progress
Philipp Schmid wrote:
>What I mean by better results is that as mentioned I ob
Hi Olaf, hi ML People :)
Am 2005-01-03 19:26 +0200 schrieb Olav Kongas:
> Here comes a new isp116x driver. I took David Brownell's
> recently updated sl811 driver and ported it to isp116x
> chips. It is considerably smaller and simpler than other
> isp116x drivers for 2.6 kernel posted to this
>
Am 2005-01-04 16:15 +0200 schrieb Olav Kongas:
> Could you please be more specific here.
Well, IIRC we postet our actual problems to this list...
> > irq65: nobody cared
>
> I think "nobody cared" means two things: either there was no
> irq handler for that irq installed, or the existing handle
Am 2005-01-04 18:04 +0200 schrieb Olav Kongas:
> Hey, you have an existing working driver and this new one.
Is the interrupt triggered forever by the isp1161a1 even after
outplugging the storage-device?
irqstat: 0x7
isp116x->irqenb: 0x12 ret value: 0x1
irqstat = isp1
Am 2005-01-04 18:04 +0200 schrieb Olav Kongas:
> 0x1 is IRQ_HANDLED
>
> Hey, you have an existing working driver and this new one.
Errr... (Having two drivers at once debugging is driving we mad):
The new driver acts weird:
With printk the driver spews
irqstat: 0x7
isp
Am 2005-01-04 22:24 +0200 schrieb Olav Kongas:
> enabled. Therefore, soon after umplugging you shouldn't see
> interrupts as all the submitted urbs should be dequeued.
Ok. I really didn't know for sure. Good point.
> These printouts look ok.
For me too. No really weird things to see.
But these
Am 2005-01-05 12:31 +0200 schrieb Olav Kongas:
> reset pin, while software reset is achieved by writing to
> proper isp116x registers and should therefore be platform
> independent.
Ok, I agree...
> Until now, I have failed to get the software reset working.
Me also :) But I am at it...
Konsti
Hi people!
Every now and then I try to get the isp116x-hcd.c driver running on my
motorola i.MX running. At the moment I assume I have not to search a bug
in isp116x-hcd.c or isp116x.h since they run on 2 or 3 other people's
boards well out of the box. So I am searching a bug in my platform or
sor
Hi!
I did some more playing with the driver.
Most often after the third plugout/plugin cycle all "nobody cared"
messages go completely away and mounting and using usb-storage devices
work fine.
By the way, the latest software reset routine (posted and fixed by olaf
IIRC) works fine. I can now use
Am 2005-01-20 18:07 +0200 schrieb Olav Kongas:
> Great that you see so many tests running flawless, at least
> for 1000 cycles.
The driver indeed runs fine, but nut with our WLAN device.
Before Debugging this I want to ask if you use your isp116x chip
interrupts level or edge triggered? I got him
Am 2005-01-20 21:32 +0200 schrieb Olav Kongas:
> I have never used the chip with edge-triggered interrupts,
> while it is working in two different designs here as level
> triggered. If your processor supports level-triggered
> interrupts, you should perhaps try using them.
Nice to know, ok. I try
rrek <[EMAIL PROTECTED]>
Organization: synertronixx GmbH
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105
Debian/1.7.5-1
X-Accept-Language: en
MIME-Version: 1.0
To: Konstantin Kletschke <[EMAIL PROTECTED]>
Subject: [Fwd: Re: [linux-usb-devel] USBTest Suit
rrek <[EMAIL PROTECTED]>
Organization: synertronixx GmbH
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105
Debian/1.7.5-1
X-Accept-Language: en
MIME-Version: 1.0
To: Konstantin Kletschke <[EMAIL PROTECTED]>
Subject: Our current status with isp116x
Content-Type
Hi Olav!
I switched on debugging in your new isp116x-hcd.c driver.
You can see successful enumeration of the wlan stick and the attempt of
the prism2_usb.ko to do something useful with it.
With debugging disabled the driver thinks "linkstatus=CONNECTED" but
wlan is not functional.
Torsten says i
Hi people!
Sorry for not informing about the state regarding the isp116x drivers.
I recently posted a lot of questions and weird issues trying to get ehis
beast stable but then came a time of vacation and illness so I will
inform now.
Olav, I took your "[PATCH] isp116x-hcd ready for review" poste
Am 2005-04-15 16:47 +0300 schrieb Olav Kongas:
> More info would be needed to pinpoint the culprit. Does this
> happen with other USB host controllers (no idea, whether you
> need to install linux-wlan-ng driver on test boxen or not)?
I will try another host controller. And no, linux-wlan-ng is
Hi Folks!
I am actually saerching a performance dececrease after I updated our
2.6.10-rc2 application.
The kernel runs on a i.MX arch (ARM9).
Until now we use this kernel with the isp116x ohci emulation driver.
After loading the ohci-hcd module prism2-usb and p80211 modules from
linux-wlan-ng a
32 matches
Mail list logo
