Hello everybody!
I have an XScale based platform with ISP 1160 on it.
I would like to connect a camera to it (with the gspcav1 driver), but the
existing driver does not support isochronous transfers with a linux 2.6 kernel.
I've search on the web a patch to add this functionality, but I haven't
Hi,
Olav Kongas wrote:
Hi,
I'm contemplating removing the option to provide clock() and
reset() functions for isp116x-hcd in platform code. However,
these functions may be necessary for power saving, which
hasn't been a priority for me as none of my platforms is
battery powered.
We have
Hi,
I'm contemplating removing the option to provide clock() and
reset() functions for isp116x-hcd in platform code. However,
these functions may be necessary for power saving, which
hasn't been a priority for me as none of my platforms is
battery powered.
clock() - if implemented by user, th
On Thu, 28 Jul 2005, Fukumoto Akira wrote:
> Hello Olav,
> some news from my development. Two facts I have found:
>
> 1. Assuming that USB needs hot plug-function the kernel always needs
> usermode-functions i.e. call_usermodehelper() to install dev-nodes for
> USB-Mass Storage-device. In my ca
On Thu, 2005-07-28 at 13:34 +0200, Fukumoto Akira wrote:
> Hello Olav,
> some news from my development. Two facts I have found:
>
> 1. Assuming that USB needs hot plug-function the kernel always needs
> usermode-functions i.e. call_usermodehelper() to install dev-nodes for
> USB-Mass Storage-devic
mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 27. Juli 2005 11:13
An: Fukumoto Akira
Cc: [email protected]
Betreff: Re: [linux-usb-devel] isp116x
On Wed, 27 Jul 2005, Fukumoto Akira wrote:
> Great Stuff !!
> dmesg looks much better now.
It was my fault: it turns out th
On Wed, 27 Jul 2005, Fukumoto Akira wrote:
> Great Stuff !!
> dmesg looks much better now.
It was my fault: it turns out that I had put up on the
webpage the 2.6.13-rc1 version of the driver instead of the
intended 2.6.12 version. I will change the driver on the
web. Sorry about wasting you
tem should occur when plugging an USB-Device?
-Ursprüngliche Nachricht-
Von: Olav Kongas [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 27. Juli 2005 07:07
An: Fukumoto Akira
Cc: [email protected]
Betreff: Re: AW: [linux-usb-devel] isp116x
On Tue, 26 Jul 2005, Fuku
On Tue, 26 Jul 2005, Fukumoto Akira wrote:
> Last first:
> brw-rw1 root root 8, 1 Jan 1 00:00 /dev/sda1
>
Thanks.
> /sys/bus/platform/devices # ls
> FEC.0 isp116x-hcd.0
>
> /sys/bus/platform/drivers # ls
> FEC isp116x-hcd <- withou
s on your configuration?
Are there any influences from plattform ppc what I have?
-Ursprüngliche Nachricht-
Von: Olav Kongas [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 26. Juli 2005 14:11
An: Fukumoto Akira
Cc: [email protected]
Betreff: Re: [linux-usb-devel] isp116x
On Tu
On Tue, 26 Jul 2005, Fukumoto Akira wrote:
>
>
> -Ursprüngliche Nachricht-
> Von: Fukumoto Akira
> Gesendet: Dienstag, 26. Juli 2005 13:25
> An: 'Olav Kongas'
> Betreff: AW: AW: AW: isp116x
>
> Everything what you describe in /sys is on board.
What do you mean by "is on board". Do
On Fri, 15 Apr 2005, Konstantin Kletschke wrote:
> Am 2005-04-15 16:47 +0300 schrieb Olav Kongas:
> > time if=a_16MB_file_on_stick of=/dev/null bs=16k
> >
> > yielded here 717 kiB/s.
>
> [EMAIL PROTECTED] ~ # time dd if=/dev/sda of=/dev/null bs=16k count=1024
> 1024+0 records in
> 1024+0 recor
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
On Fri, 15 Apr 2005, Lothar Wassmann wrote:
> Hi,
>
> On Fri, 15 Apr 2005, Olav Kongas wrote:
> > Leaving aside what may be "the best" way to measure the USB
> > performance, I did it with usb-2.0 memory stick, which was
> > the only device attached at the measurement time. With this
> > con
Hi,
On Fri, 15 Apr 2005, Olav Kongas wrote:
> Leaving aside what may be "the best" way to measure the USB
> performance, I did it with usb-2.0 memory stick, which was
> the only device attached at the measurement time. With this
> controller, it's in full speed mode, of course. Mounting a
> st
On Fri, 15 Apr 2005, Konstantin Kletschke wrote:
> 1.) In 10% of all plug events of the WLAN stick the usb core tells
> "Device Descriptor Read Error" with both of the ohci emulation framework
> and with the isp116x-hcd driver. Is it save to blame the WLAN stick
> itself to be being buggy? In al
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
On Friday 04 March 2005 5:32 am, Ian Campbell wrote:
>
> There seem to be a few strange things about the sl811 driver that I
> don't understand, and the changelog says compile tested only so I'll
> bring them up here, and CC you David, since your name is in the
> signed-off-by.
Yes, and you might
Hi,
I have finally put up the possibly last version of the
isp116x driver for 2.6.10: http://www.artecdesign.ee/~ok/isp116x/
A week ago I discussed off-list with David of how to proceed
with the driver. First I will try to improve the
suspend/resume support, which exists currently only for
ports
Hi Olav,
I don't know if you've done any of this already, but I rather
mechanically created the two attached patches by blindly following the
patches made to the sl811h driver... Not really a recipe for success I
admit :-) Fortunately it does seem to work, after some tweaking. I'm not
sure I see a
Hi Olav,
I've been trying to get a USB->Ethernet dongle working on my platofrm
with an isp1160. The dongle is a Belkin one[0] that uses the PEGASUS II
driver. The dongle works fine on my workstation with 2.6.10 so I'm
assuming that part of the driver is OK. (I've backported some pegasus
changes fr
On Fri, 21 Jan 2005, Alan Stern wrote:
> > What can cause khubd sleeping uninterruptibly? How do debug
> > this?
> >
> > Below is a log about how it all happens. Hints are needed
> > and appreciated.
>
> This was a locking bug in the hub driver for 2.6.9. It has been fixed in
> 2.6.10 (in fact t
On Fri, 21 Jan 2005, Olav Kongas wrote:
> Hi,
>
> When I do plug/unplug cycles with a particular memory stick,
> which has an embedded hub, I get easily khubd hanging into
> uninterruptible sleep. I have made about 100 plug/unplug
> cycles for each of the following devices/combinations
> (keyboar
On Friday 21 January 2005 9:49 am, Olav Kongas wrote:
>
> I have kept an eye on the hcd glue changes and they are
> indeed easy to incorporate. The problem is that the driver
> is still buggy.
It does take a while to get USB controller drivers working!
Though it sounds like you're almost past the
On Fri, 21 Jan 2005, Olav Kongas wrote:
>
> Hi,
>
> When I do plug/unplug cycles with a particular memory stick,
> which has an embedded hub, I get easily khubd hanging into
> uninterruptible sleep. I have made about 100 plug/unplug
Forgot to mention, that the testing/logging was done under
2.6
On Thu, 20 Jan 2005, David Brownell wrote:
> I think those 2.6.11 changes can all be characterized as
> streamlining the HCD glue, which will make adding new HCDs
> easier in the future. Most of the 2.4.11 changes are ones
> that should trigger compile time errors with older code.
> So prepping
Hi,
When I do plug/unplug cycles with a particular memory stick,
which has an embedded hub, I get easily khubd hanging into
uninterruptible sleep. I have made about 100 plug/unplug
cycles for each of the following devices/combinations
(keyboard, externalhub+keyboard [plugging/unplugging hub
cable
On Thu, 20 Jan 2005, Philipp Schmid wrote:
> The only non-porting changes (from 2.6.6 - I can't upgrade because of
> customer requirements ...) are the following. As isp116x_write_data16() is
> already correctly swapping bytes for big/little endian, but the PTD payload
> is a byte stream, I nee
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
: [email protected]
Subject: RE: [linux-usb-devel] isp116x-hcd update
On Thu, 20 Jan 2005, Philipp Schmid wrote:
>
> Yes ... that did it. I've got my USB hard drive back and can do kernel
> compiles on it. However, I don't quite see how that change wou
On Thu, 20 Jan 2005, Konstantin Kletschke wrote:
> 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 edge triggering this day
> but while playing around further (the irq no
On Thursday 20 January 2005 8:07 am, Olav Kongas wrote:
>
> What happened for OUT transfers longer than
> MAX_TRANSFER_SIZE_FULLSPEED was that the first PTD was sent
> and then, without "break-ing" there, the urb was finished
> with return code 0. With this bug, the usbtests worked (at
> least in
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
On Thu, 20 Jan 2005, Philipp Schmid wrote:
>
> Yes ... that did it. I've got my USB hard drive back and can do kernel
> compiles on it. However, I don't quite see how that change would affect
> anything except for preventing the break call under the USB_PID_IN/OUT case
> ...
What happened for
, January 20, 2005 9:35 AM
To: Philipp Schmid
Cc: [email protected]
Subject: RE: [linux-usb-devel] isp116x-hcd update
On Wed, 19 Jan 2005, Philipp Schmid wrote:
> I have captured a few dumps when this failure is happening. It ~always~
> happens to the same type of transfer
On Wed, 19 Jan 2005, Philipp Schmid wrote:
> I have captured a few dumps when this failure is happening. It ~always~
> happens to the same type of transfer:
>
> Enqueue: FA 2 ep2in bulk: len 13 short_ok
> pack_fifo @ c5d6/2e9c fmrem
> CC=f EP=2 DIR=2 CNT=0 LEN=13 MPS=64 TGL=1 ACT=1 FA=2 SPD=0 L
DBG("%d: nextpid %d, status %d, err
>
if (ep->nextpid == USB_PID_ACK)
>
ep->nextpid = 0;
spin_unlock(&urb->lock);
spin_unlock(&
On Tue, 18 Jan 2005, Philipp Schmid wrote:
> usb-storage: usb_stor_bulk_transfer_sglist: xfer 1024 bytes, 1 entries
> usb-storage: Status code 0; transferred 832/1024 <= single PTD
> usb-storage: -- short transfer
> usb-storage: Bulk data transfer result 0x1
I haven't seen these mes
age-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Olav
Kongas
Sent: Monday, January 17, 2005 6:39 AM
To: [email protected]
Subject: [linux-usb-devel] isp116x-hcd update
Recently there has been some progress with the isp116x
driver. Running usbtests on the dr
Recently there has been some progress with the isp116x
driver. Running usbtests on the driver has revealed bugs,
some of which are fixed by now. The driver has been
under test #10 few nights without errors and I have had all
other tests including unlink and halt tests running
thousands of cycles
On Fri, 2005-01-07 at 14:13 +0200, Olav Kongas wrote:
> Here comes an updated sw reset code.
Thanks, works for me here.
Ian.
--
Ian Campbell, Senior Design Engineer
Web: http://www.arcom.com
Arcom, Clifton Road,Direct: +44 (0)1223 403
Here comes an updated sw reset code. The previous one
accessed registers between spin_{lock,unlock}_irq() pair,
which was a bug if called from isp116x_stop() with irqs
disabled.
I also moved the mdelay(1) before the test in the loop. On
one of my boards, the reset caused trouble while it was
clai
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
> At first I am going to implement a small software Reset Routine
> between the /* */ in my platform setup.
> I hope a software Reset is as good as a Hardware Reset there.
I propose that we use terminology as it is in the isp116x
datasheets: hardware reset means asserting the isp116x's
reset pin,
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
> Is the interrupt triggered forever by the isp1161a1 even after
> outplugging the storage-device?
If there are INT urbs submitted to the driver then SOF
interrupt is enabled and ATL interrupt is disabled.
Otherwise (which includes control and/or bulk urbs or no
urbs at all) the SOF interrupt is
On Wed, 22 Dec 2004, Torsten Koschorrek wrote:
> @all isp1xxx users, can you tell us the name of the chip you're working
> with! I have an isp1161a1. Olav has also an isp116x, Lothar has a 1362
> as far as I know. And the others?
I use 1160.
Olav
-
On Wed, 22 Dec 2004, Philipp Schmid wrote:
> What I mean by better results is that as mentioned I observe PTS needing to
> be resubmitted repeatedly. When handling SOF and ATL interrupts, I've
> observed 3 cases:
>
> (1) PTDs are resubmitted multiple times but get handled eventually before
> US
> For me performance is not a requirement, correct
> operation is.
..
> I also have INTL traffic going to some extend.
Same here. At least, I haven't run into any problems with any
problems since I tweaked the buffer setup.
> I am not entirely finished debugging everything yet but I have
> the f
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
ED]
Sent: Wednesday, December 22, 2004 4:09 AM
To: Philipp Schmid
Cc: [email protected]
Subject: RE: [linux-usb-devel] ISP116x / 1362 driver progress
Hi Philipp,
Thank you for the comprehensive overview.
> A couple of observations:
>
> (a) I find many PTDS have to
Hi Philipp,
Thank you for the comprehensive overview.
> A couple of observations:
>
> (a) I find many PTDS have to be resubmitted many times before they get
> handled by the device even if they are finished submitting early in the
> frame remaining cycle.
Transfers start after subsequent SOF aft
riginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Michael
Sent: Tuesday, December 21, 2004 2:43 PM
To: Olav Kongas; Dimitris Lampridis
Cc: [email protected]
Subject: [linux-usb-devel] ISP116x / 1362 driver progress
Hi guys.
I haven't seen anythi
Hi,
On Tue, 21 Dec 2004, Torsten Koschorrek wrote:
> Michael wrote:
> > Olav mentioned perhaps rewriting the driver, based on the new
> > sl811-hcd driver, which I agree is a better solution.
> >
Yes, I am working on a simpler 116x driver. The driver is
not functional yet, but the work is progr
Michael wrote:
Olav mentioned perhaps rewriting the driver, based on the new
sl811-hcd driver, which I agree is a better solution.
Yes, he want's to write it only for the 116x, as far as I read and
understood it. I think, it would be a very good idea to write TWO
drivers, one for the 116x and one f
Hi guys.
I haven't seen anything on the list recently regarding this driver,
and I was wondering how you were doing.
Olav mentioned perhaps rewriting the driver, based on the new
sl811-hcd driver, which I agree is a better solution.
I would like to see this, but I can't help much (or, atleast rig
On Thu, 2 Dec 2004, Konstantin Kletschke wrote:
> 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?
Yes.
Olav
--
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
> 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_size 0, xfer_size_real 0
> process_td: alloc_ptd returned 0
> process_td: dir=1 ed->hwINFO=0040(0), td->hwINFO=f308(1)
> td a
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 some devices!
Heureka
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
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 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
Konstantin Kletschke
Sent: Tuesday, November 30, 2004 7:31 AM
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 t
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.
On Tue, 30 Nov 2004, Konstantin Kletschke wrote:
> 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 resettin
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...
> >
> What I forgot to ask, on what processors are you using the isp1362 or
> 1161 HCs?
I am using an ARM-based SoC, lh7a400. Most of us have told
what each of us uses. It is in the archive.
> void ohci_isp1362_hw_reset(int id, int set)
> {
> }
Just wondering, are you using software reset or no rese
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
Hi,
A reasonable setup for 116x for this driver would be ...
> isp1362-ohci isp1362-ohci0: ISP116x Memory usage:
> isp1362-ohci isp1362-ohci0: ISTL: 2 * 512: 1024
ISTL: 2 * 0 , because the driver currently does not support
iso transfers
> isp1362-ohci isp1362-ohci0: INTL: 4 * 64: 288
On Monday 29 November 2004 07:19, Konstantin Kletschke wrote:
> Hi there!
Hi back ... :)
> As you know, the usb changes between 2.6.9 and 2.6.10 are quite huge,
> hc_start and hc_reset are gone now :(
Those are not "USB changes", they're OHCI-internal ones.
However, there are USB changes in 2.
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 = {
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
Olav Kongas wrote:
Hi,
i've Lothar's driver ohci-isp1362 working for my isp1161a. The init is
ok and i can read some registers. I was searching for your patch in the
mailing list for the isp116x but didn't find it. Is it possible to mail
the patch to me? After applying your patch i can help lookin
Hi,
> I've turned off all my debug info to see if I see the same symptoms of
> addressing address 0. Without debug info I can't easily see what's going
> on, but my USB mouse still initializes fine. So I am assuming I am not
> seeing this problem.
Thanks for trying to help. It is solved now. Th
Hi,
> i've Lothar's driver ohci-isp1362 working for my isp1161a. The init is
> ok and i can read some registers. I was searching for your patch in the
> mailing list for the isp116x but didn't find it. Is it possible to mail
> the patch to me? After applying your patch i can help looking for the
>
Hi,
First, sorry about the bogus e-mail I just sent into this
thread.
> I reported some progress with the driver in my last e-mail
> (can successfully mount/read/write compact flashes inserted
> in a Trendnet's compact flash reader). But all this only
> with the debug info on. There is probably a
Hi,
On Tue, 23 Nov 2004 09:23:33 +0200 (EET), Olav Kongas <[EMAIL PROTECTED]>
wrote:
I tried to find the cause but was not very sucessfull.
The Problem lies somewhere in hci_submit_urb
and a call of mdelay(6) is sufficient to get everything working.
mdelay(4) is not enough. I am not quite happy
Hi Christoph,
> Well, I am not working with the new 2.6 driver, but with
> hc_isp116x v 0.9.5 on a 2.4.26 kernel
> (because the v 0.9.5 was the only version I got a bluetooth USB
> dongle working).
>
> But this sounds _very_ similar to the problem I had with the driver.
> I postet to this list abo
Hi,
On Mon, 22 Nov 2004 10:00:42 +0200 (EET), Olav Kongas <[EMAIL PROTECTED]>
wrote:
I reported some progress with the driver in my last e-mail
(can successfully mount/read/write compact flashes inserted
in a Trendnet's compact flash reader). But all this only
with the debug info on. There is pr
mitris
Lampridis; Michael
Subject: [linux-usb-devel] isp116x debug info/timing problem?
Hi,
I reported some progress with the driver in my last e-mail
(can successfully mount/read/write compact flashes inserted
in a Trendnet's compact flash reader). But all this only
with the debug info on. Ther
Olav Kongas wrote:
Hi,
I reported some progress with the driver in my last e-mail
(can successfully mount/read/write compact flashes inserted
in a Trendnet's compact flash reader). But all this only
with the debug info on. There is probably a timing problem
somewhere so that if the debug info is re
Hi,
I reported some progress with the driver in my last e-mail
(can successfully mount/read/write compact flashes inserted
in a Trendnet's compact flash reader). But all this only
with the debug info on. There is probably a timing problem
somewhere so that if the debug info is removed (DPRINTK
dec
Michael wrote:
--- Torsten Koschorrek <[EMAIL PROTECTED]> wrote:
I'm trying to port the isp_116x_bingo-driver to kernel 2.6.9 on
Architecture ARM, Mach imx.
I have success in compiling and loading the driver. In the
Init-Process the driver reads the Chip-ID. I also know, that the
interrupts are
Hi list,
I'm trying to port the isp_116x_bingo-driver to kernel 2.6.9 on
Architecture ARM, Mach imx.
I have success in compiling and loading the driver. In the Init-Process
the driver reads the Chip-ID. I also know, that the interrupts are
working. But there are some problems.
Problem 1:
I get
Hello List,
I compiled the BINGO version.
but it is the same result as I had with TANGO before.
for all non bluetooth specific it seems to work.
but for bluetooth it's not working:
(it works with isp116x Version 0.9.5 (10/28/2001))
[EMAIL PROTECTED] root# hciconfig -a
hci0: Type: USB
BD
ehalf Of Ting
Wang
Sent: 17 September 2004 06:41
To: [EMAIL PROTECTED]
Subject: [linux-usb-devel] isp116x bingo version release, hope may help
you : )
Hi :
I based my version on tango version. In my version mainly change
isoc transfer part. On my platform ( Intel Sitsang Evaluation Board
Hi :
I based my version on tango version. In my version mainly change
isoc transfer part. On my platform ( Intel Sitsang Evaluation Board
with PXA255 arm-linux-2.4.19-rmk7 ) the image is fluent even under
severe system load ( CPU usage upto 99%, CF wifi bit rate:
300~400kb/s). Special thanks
On Fri, 3 Sep 2004, Andy Heaton wrote:
> > If you are mounting a filesystem for the copy, then why are you unplugging
> > the device while it is still mounted? It's not at all surprising that you
> > end up with a nasty error.
>
> Because it's the sort of thing a user would do. I'm working on a
Hi,
I'm having a problem with the ISP116x driver, just wondered if anyone
else
had come across this.
I connect a memory stick into the USB, and copy a large file (say 50MB)
onto
it. Part way through the copy I unplug the memory stick. My system then
hangs. If I unplug the memory stick early in t
On Thu, 2 Sep 2004, Andy Heaton wrote:
> Hi,
>
> I'm having a problem with the ISP116x driver, just wondered if anyone else
> had come across this.
>
> I connect a memory stick into the USB, and copy a large file (say 50MB) onto
> it. Part way through the copy I unplug the memory stick. My sys
Hi,
I'm having a problem with the ISP116x driver, just wondered if anyone else
had come across this.
I connect a memory stick into the USB, and copy a large file (say 50MB) onto
it. Part way through the copy I unplug the memory stick. My system then
hangs. If I unplug the memory stick early in
Hi, everybody
I find the condition "bstat & ITL1(0)BufferDone" in hc_interrupt() can
never be met.
But when i add "bstat & ITL1(0)BufferFull"flags,it become true in turn
with
certain interval.What the possible problem is? Did i not set the register
correctly,
or it has problems with hardware?
Hi,
I use isp1161 to capture image with ov511 camera ,and I modifid the
HCD(0.9.5) according the Tango version.the platform is sitsagn board
(pxa250),linux--2.4.19.
I traced the hc_isp116x.c and hc_simple.c .The "frame_number"
increases regularly the fist secends after the app start.Then
Try reading the FAQ.
On Mon, 26 Jul 2004 [EMAIL PROTECTED] wrote:
> No one knows what happened??
>
> I am really in a hurry, Plz give me a hand!!
>
> thanks!
>
>
>
> In your mail:
>
> >Hello everyone,
>
> >
>
> >
>
> >
>
> >I got a surprised error after I "modprobe hc_isp116x", it seems that
No one knows what happened??
I am really in a hurry, Plz give me a hand!!
thanks!
In your mail:
>Hello everyone,
>
>
>
>I got a surprised error after I "modprobe hc_isp116x", it seems that
there
>is no interrupt occurred after I pluged the USB mouse.
>
>___
>
Hello everyone,
I got a surprised error after I "modprobe hc_isp116x", it seems that there
is no interrupt occurred after I pluged the USB mouse.
___
This is the msg:
#modprobe hc_isp116x
-
hc_isp116
> Have you tested with multiple USB devices? I'm curious as to how it
scales.
>
We have used a couple of concurrent USB devices, and performance doesn't
crater.
I can't really be more specific than that at the moment. We generally use
webcams and
printers as second devices. Neither allows easy mea
On Wednesday 11 June 2003 09:19 pm, Eric Nelson wrote:
> > Is 600KB/s during isochronous xfers? Using a PCI based USB host the best
>
> I've
>
> > seen for bulk xfers with the Dell Axim PDA is 200KB/sec.
>
> No. ATL transfers via an ethernet device from a Linux PC, of course :).
Have you tested
> Is 600KB/s during isochronous xfers? Using a PCI based USB host the best
I've
> seen for bulk xfers with the Dell Axim PDA is 200KB/sec.
>
No. ATL transfers via an ethernet device from a Linux PC, of course :).
This is roughly the same performance we see using a laptop performing
the same trans
1 - 100 of 103 matches
Mail list logo
