problems on isp1362 driver

problems on isp1362 driver

[David Zhang]

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

Hi all,
 
We are using Philips ISP1362 USB controller on WinCE 4.2.  It seems that we
are encountering "ATL interrupt" missing problem.  I am wondering if any of
you ever had the similar problem.
 
Any suggestions how to solve the problem?  Thanks a lot in advance.
 

David Zhang 


[-- Attachment #2: Type: text/html, Size: 1073 bytes --]

Re: problems on isp1362 driver

[David Jander]

On Friday 15 July 2005 02:14, David Zhang wrote:
>[...]
> We are using Philips ISP1362 USB controller on WinCE 4.2.  It seems that we
> are encountering "ATL interrupt" missing problem.  I am wondering if any of
> you ever had the similar problem.

Where does this driver come from? Does it have anything to do with linux 
kernel versions of that driver? If so, which one, 2.4 or 2.6?

I don't know WinCE, much less how drivers work in WinCE. Please specify what's 
the relationship (or expected relationship) with linux. In any case, you'd 
have to tell more details about the problem you're experiencing, otherwise 
it's unlikely someone here can help you.

I am using the isp116x HCD driver from kernel 2.6 now with a isp1160 chip, and 
it runs fine. I suppose you are talking about the Host part of the 1362?

Greetings,

-- 
David Jander

problems on isp1362 driver

[lu]

Hi all,

We are using Philips ISP1362 usb controller on our ppc-embedded system. We
have ported the phlips's driver, PHCI, to ppc. The Philips linux driver is
that of  2002.

Following are problems tha we've found in our  test:

1) ATL Interrupt doesn't work correctly. We have to use
ATL_THRESHOLD_TIMEOUT, that has the minimun resolution 1 msec, to bypass it.

2) The latency from PTD completion. From a usb frame analyzer we have seen
that the controller has gaps between every 4 64-bytes frames for 265 bytes
PTD configured in bulk transmission. The limit of 265 byte for PTD is due to
the end-point number.

3) The isochronous mode doesn' t work. That we've seen was we were loop on
frame number, so the machine went to hang!

>From the list I've seen that Wolfgang Denk  has worked for that driver and
test is for a lot of devices. I'd like to know from Wolfgang which driver is
used? Is the driver that you are using is open source? Where can we get it?
Thanks in advance!
Jianliang Lu

Re: problems on isp1362 driver

[Wolfgang Denk]

Dear Jianliang Lu,

in message <000001c57347$04a45d00$07070a0a@luj> you wrote:
> 
> We are using Philips ISP1362 usb controller on our ppc-embedded system. We
> have ported the phlips's driver, PHCI, to ppc. The Philips linux driver is
> that of  2002.

You cannot do that. The  Philips  driver  comes  uner  a  proprietary
license  which  is  incompatible with the GPL. You must not use their
driver in the context of a Linux kernel or any other GPLed  software.
You  are  either  violating  the  GPL,  or  the  Philips  license. Be
careful!!!

> >From the list I've seen that Wolfgang Denk  has worked for that driver and

No!!! We never had any access to the Philips drivers. We are proud of
using Free Software exclusively and will not accepts such a license.

> test is for a lot of devices. I'd like to know from Wolfgang which driver is
> used? Is the driver that you are using is open source? Where can we get it?

Our version of the driver is Free Software under GPL. It is included
in the linuxppc_2_4_devel module on our CVS server, see
http://www.denx.de/re/linux.html


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
       There is enough for the need of everyone in this world,
       but not for the greed of everyone.     - Mahatma Gandhi

Re: problems on isp1362 driver

[David Jander]

On Friday 17 June 2005 21:12, Wolfgang Denk wrote:
> in message <000001c57347$04a45d00$07070a0a@luj> you wrote:
> > We are using Philips ISP1362 usb controller on our ppc-embedded system.
> > We have ported the phlips's driver, PHCI, to ppc. The Philips linux
> > driver is that of  2002.
>
> You cannot do that. The  Philips  driver  comes  uner  a  proprietary
> license  which  is  incompatible with the GPL. You must not use their
> driver in the context of a Linux kernel or any other GPLed  software.
> You  are  either  violating  the  GPL,  or  the  Philips  license. Be
> careful!!!

IANAL, but I think theoretically at least, it should be possible, if you 
manage to craft sort of a "GPL abstraction layer" around the philips driver, 
to shield it from "GPL influence" in the kernel, just like Nvidia and others 
do. To the letter of the GPL that is not possible, but AFAIK the linux kernel 
license grants an exception that permits binary-only drivers for instance.
Anyway, it probably is a bad and dangerous idea to try to pull this off. As 
for me, I decided it is much safer to stay as far away as possible from the 
philips source. Looking at it could be fatal for an OSS-coder like me (my 
eyes could get poisoned).
Here goes a big "BOOOO" to Philips for doing this in the first place :-(

Greetings,

-- 
David Jander

Re: problems on isp1362 driver

[Wolfgang Denk]

In message <200506201238.19121.david.jander@protonic.nl> you wrote:
>
> IANAL, but I think theoretically at least, it should be possible, if you 
> manage to craft sort of a "GPL abstraction layer" around the philips driver, 

No, you cannot even do that. The Philips license explicitely  forbids
to  "combine Open Source Software with the Software or any derivative
work thereof". This effectively prevents any use of the driver  in  a
Linux  environment. Of course you can now ask which sense it makes to
release a Linux driver under such a license, but please don't ask me.
Ask the id^H^Hlawyers at Philips.

> do. To the letter of the GPL that is not possible, but AFAIK the linux kernel 
> license grants an exception that permits binary-only drivers for instance.

Please read again. This is allowed only for  pre-existing  code  that
was not written for Linux. And even then it's not really clean. BUt I
seriously doubt that the Philips Linux driver can claim to fall under
this exception.

My interpretation is that an anal-restrictive lawyer came up  with  a
license  once,  and  some  other people applied this license to Linux
drivers without any thinking. If you want to  complain,  complain  at
Philips.  Alternatively,  just  don't  use  their code. If necessary,
don't use their hardware  either.  There  are  other  solutions  with
better software support.

> for me, I decided it is much safer to stay as far away as possible from the 
> philips source. Looking at it could be fatal for an OSS-coder like me (my 
> eyes could get poisoned).
> Here goes a big "BOOOO" to Philips for doing this in the first place :-(

100% ACK from me.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
All your people must learn before you can reach for the stars.
	-- Kirk, "The Gamesters of Triskelion", stardate 3259.2