Re: [linux-usb-devel] [PATCH] PXA27x UDC driver.

2007-07-10 Thread Lothar Wassmann
ng the > following warnings from the compiler: > [...] > > Do you know how I can resolve this? > ioremap() the memory area for the UDC registers and use an __iomem cookie. Lothar Wassmann -- ___ Ka-Ro electronics GmbH | Pas

Re: [linux-usb-devel] [patch 2.6.17-git] pxa2xx_udc understands GPIO based VBUS sensing

2006-06-30 Thread Lothar Wassmann
> morph (0|bits) into 0 so the test succeeds. > Unless the chosen bit happens to be 'GPIO_IN', which is defined as 0. Lothar Wassmann Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easie

Re: [linux-usb-devel] [patch 2.6.17-git] pxa2xx_udc understands GPIO based VBUS sensing

2006-06-30 Thread Lothar Wassmann
Hi, > + if (mach->gpio_pullup) > + pxa_gpio_set(mach->gpio_pullup, 0); [...] > + if (mach->gpio_pullup) > + pxa_gpio_set(mach->gpio_pullup, 1); > What if a hardware designer chooses to use GPIO '0' for one of these functions

Re: [linux-usb-devel] Advices needed for implementing a HCD for a strange HC

2005-07-07 Thread Lothar Wassmann
list (like > in UHCI) which allows to link transactions that will make up a single frame. > There's no change bit report, no root hub, only one port. > > I'm wondering if it's possible to write a driver with such hardware using > usbcore... > Have a look at driv

Re: [linux-usb-devel] Re: Troubles with 116x driver on PXA255 platform

2005-06-30 Thread Lothar Wassmann
Hi, Michael Kelly writes: > At 06:24 AM 6/30/2005, Lothar Wassmann wrote: > >Hi, > > > >Michael Kelly writes: > > > Bill, > > > > > > One issue with the PXA255 edge triggering is that you need > > > to be sure you poll the state of the int

Re: [linux-usb-devel] Re: Troubles with 116x driver on PXA255 platform

2005-06-30 Thread Lothar Wassmann
d when another interrupt condition exists when interrupts are reenabled. The ISP116x interrupt handler does it this way. Lothar Wassmann --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple t

Re: [linux-usb-devel] Re: Troubles with 116x driver on PXA255 platform

2005-06-30 Thread Lothar Wassmann
e PXA requires a minimum pulse width of 1 microsecond (Chapter 4-12 of the PXA255 Developers Manual) on a GPIO pin for proper edge detection. The ISP116x generates a pulse of 167ns in edge triggered mode. Thus you cannot use the edge triggered mode of the ISP116x with a PXA processor. Lothar Wassmann ---

Re: [linux-usb-devel] isp1362

2005-06-07 Thread Lothar Wassmann
lower 5 bits) and the interval in the PTD and the chip will only submit the PTD when the lower bits of the current frame number match the Starting Frame bits in the PTD. This is just like OHCI does. Lothar Wassmann --- This SF.Net email is sp

Re: [linux-usb-devel] isp1362

2005-06-07 Thread Lothar Wassmann
scheduled without CPU intervention (as long as they are NAKed by the device). Thus the SOF interrupt is not necessary for INT transfers. Lothar Wassmann --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a proje

Re: [linux-usb-devel] ISP1362 HCD detects, but no interrupts

2005-05-03 Thread Lothar Wassmann
ason. > > Should I be setting the IRQ falling/rising edge with set_irq_type? > It should of course match the 'int_act_high' setting in the platform_data. Lothar Wassmann --- This SF.Net email is sponsored by: NEC IT Guy Game

Re: [linux-usb-devel] ISP1362 HCD detects, but no interrupts

2005-05-02 Thread Lothar Wassmann
ip generates in 'edge triggered mode' may be too short to be detected by the CPU (which is e.g. true for PXA2xx). Lothar Wassmann --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your b

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-29 Thread Lothar Wassmann
Andre Renaud writes: > On Fri, 2005-04-22 at 09:21 +0200, Lothar Wassmann wrote: > > What type of memory access do you use? I'm using VLIO with the MSC > > setting 0x7f8c at 99.53MHz memclk. This is probably the only setup > > that can guarantee the chips timing requi

Re: [linux-usb-devel] isp1362-hcd: "irq24: nobody cared"

2005-04-28 Thread Lothar Wassmann
When this delay macro is undefined insw/outsw will be used, with the macro defined (even if empty) a loop around read_data16/write_data16 will be used like in your case. Lothar Wassmann --- SF.Net email is sponsored by: Tell us your software dev

Re: [linux-usb-devel] isp1362-hcd: "irq24: nobody cared" and "missing status stages"

2005-04-28 Thread Lothar Wassmann
oping > with modules makes more sense. > If a module cannot be unloaded or behaves differently after reload it most likely did something fishy that you probably would never notice when building the driver into the kernel. Lothar Wassmann ---

Re: [linux-usb-devel] isp1362-hcd: "irq24: nobody cared" and "missing status stages"

2005-04-27 Thread Lothar Wassmann
u still have problems with the access timing) or by clearing the interrupt condition outside the interrupt handler. You could try to reread the status register to make sure you don't read bogus values. Can you send a complete log of the messages? Lothar Wassmann --

[linux-usb-devel] Re: isp1362-hcd driver feedback

2005-04-27 Thread Lothar Wassmann
isp1362_read_data16(isp1362_hcd); > +*dp++ = (u8)data; > +len--; > +} > +#endif > } The '(len > 0)' case should be the same under all circumstances, so the '#endif' could be placed right before it. Lothar Wassmann

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-22 Thread Lothar Wassmann
flash memory, but > never mind, it works. > The main portion of the delay is probably accounted for by flushing and refilling the memory controllers pipeline. Thus the latency of the memory controller is the important factor, not the cycle time of an individual cycle.

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-22 Thread Lothar Wassmann
hz memory clock, an uncached read > from SDRAM can theoretically take ~70ns right? > An SDRAM memory cycle may be 70ns, but UNCACHED_PHYS_0 is mapped to phys addr 0x which is the static CS0 (usually FLASH ROM) on PXA2xx. Lothar Wassmann

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-22 Thread Lothar Wassmann
e that the access is actually done. > after this you do not need some looping to ensure a ~460ns delay. > On a PCA-263 with the core clock at 500Mhz, I am using the > following code: > I'm getting ~700ns delay with the UNCACHED_PHYS_0 access alone. Lothar Wassmann --

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-22 Thread Lothar Wassmann
requirements. Be aware that VLIO uses nPWE instead of nWE as write strobe. Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which produc

[linux-usb-devel] Re: isp1362-hcd and XFERCTR

2005-04-20 Thread Lothar Wassmann
ERCTR is only required when accessing the buffer through the ATL/INTL/ISTL PORT registers. Lothar Wassmann --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in cr

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-20 Thread Lothar Wassmann
you need additional delays between each access that should not be a problem. The crucial point is the delay between writing the addr reg and accessing the data reg. This delay of 300ns/462ns most probably cannot be accomplished with the setup of the memory controller alone. Lothar Wassmann

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-19 Thread Lothar Wassmann
ether CLKRDY should be asserted after software reset. It says the chip is put into USB_SUSPEND state after asserting HCR. CLKRDY signals the wakeup of the chip from suspend mode. Does it work, if you don't check for CLKRDY? Maybe Olav can comme

Re: [linux-usb-devel] isp1362 hw connection

2005-04-19 Thread Lothar Wassmann
necessary delay, so that no extra software delay was necessary. Lothar Wassmann --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and

Re: [linux-usb-devel] [RFC] isp1362-hcd driver for 2.6.11-mm2

2005-04-18 Thread Lothar Wassmann
mach-lh7a40x/arch-oscar.c file, where I > specify that I have this platform device. > Aaargh. It was some last minute cleanup that lead to this crash. I only compiled with CONFIG_USB_DEBUG disabled after this change which disables the BUG_ON() checking. Lothar Wassmann --- linux-2.6.11-mm2/dr

Re: [linux-usb-devel] isp116x-hcd on ARM9

2005-04-15 Thread Lothar Wassmann
es the influence of the file systems drivers and caches. It also eliminates the need to mount the file system and create a testfile. HTH, Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on h

Re: [linux-usb-devel] Re: [PATCH as502 (3/5)] UHCI: Add root hub states

2005-04-14 Thread Lothar Wassmann
automagically ensures the necessary delay). Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start

RE: [linux-usb-devel] Original drivers for ISP1362 by Philips

2005-04-07 Thread Lothar Wassmann
doing some cleanups and will post it hopefully within the next days (or maybe hours...). Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover

Re: [linux-usb-devel] Problems with usbtest and pxa2xx_udc

2005-03-23 Thread Lothar Wassmann
the controller will spread the packets across multiple frames without errors. There is normally no need to check the allocated frame time by software. Nevertheless I tried to move the SETUP transfer away from the end of the frame by checking the HcFmRema

Re: [linux-usb-devel] format=flowed messes up patches

2005-03-22 Thread Lothar Wassmann
sent attached, of course. > > Please let me know, if you want me to resend the patch. > No thanks, not necessary. There were only few lines that needed manual care. Lothar Wassmann --- This SF.net email is sponsored by: 2005

[linux-usb-devel] Problems with usbtest and pxa2xx_udc

2005-03-21 Thread Lothar Wassmann
;feature" of the PXA UDC hardware. Can anyone comment on this? Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly l

Re: [linux-usb-devel] [PATCH] isp116x-hcd ready for review

2005-03-21 Thread Lothar Wassmann
rivers/usb/host/Kconfig 2005-03-18 > 18:19:08.0 +0200 > @@ -49,6 +49,19 @@ config USB_EHCI_ROOT_HUB_TT > ^ here should be a space. I think this: |Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Re: [linux-usb-devel] ISP1362 driver status

2005-02-17 Thread Lothar Wassmann
've got some new hardware with an ISP1362 here and just started to adapt the 116x driver for it. Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users

[linux-usb-devel] copy/paste error in sl811-hcd.c

2005-01-12 Thread Lothar Wassmann
->data_reg = ioremap(data->start, resource_len(addr)); + sl811->data_reg = ioremap(data->start, resource_len(data)); if (sl811->data_reg == NULL) { status = -ENOMEM; goto fail;

Re: [linux-usb-devel] Re: isp1362 driver - BUG_ON(xfer_size < mps)

2004-12-17 Thread Lothar Wassmann
dev->intl_queue.num_bufs = 1; > dev->intl_queue.blk_size = 64; > > That seemed to fix it. Performance isn't a big issue, so I think > this will be okay. > It's not a workaround, it's The Solution(TM) ;-) Lothar Wassmann -

Re: [linux-usb-devel] Re: isp1362 driver - BUG_ON(xfer_size < mps)

2004-12-17 Thread Lothar Wassmann
Hi David, > On Friday 17 December 2004 6:53 am, Lothar Wassmann wrote: > > Hi David, > > > > > On Friday 17 December 2004 1:51 am, Lothar Wassmann wrote: > > > > > xfer_size = ptd_xfer_size(ptd_q, xfer_type, len); > > > > > printk

Re: [linux-usb-devel] Re: isp1362 driver - BUG_ON(xfer_size < mps)

2004-12-17 Thread Lothar Wassmann
Hi David, > On Friday 17 December 2004 1:51 am, Lothar Wassmann wrote: > > > xfer_size = ptd_xfer_size(ptd_q, xfer_type, len); > > > printk("len = %d, xfer_size = %d, mps = %d, xfer_type = %d\n", > > > len, xfer_size, mps, xfer_type); >

[linux-usb-devel] Re: isp1362 driver - BUG_ON(xfer_size < mps)

2004-12-17 Thread Lothar Wassmann
Hi Michael, > Hi. I'm using the ohci-isp1362 driver, and I'm finally getting it > working. However, I can make it crash every time I use a > usb-serial adapter. > > I seem to trigger the BUG_ON(xfer_size < mps) in process_td. > (ohci-isp1362-emu.c) It seems the null pointer dereference is > cau

Re: [linux-usb-devel] first steps with our isp1161a1

2004-12-02 Thread Lothar Wassmann
WARN_ON(1); > return; > } > > Why is the warning/error generated and how to avoid this? > TD_BUSY is set, when the driver starts processing a TD and reset after it has been released to the OHCI HCD. So if it

Re: [linux-usb-devel] hanging bug with ohci-isp1362

2004-11-29 Thread Lothar Wassmann
s? > The driver sets this condition code to mark TDs that he is already processing to avoid reprocessing them. Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products fr

Re: [linux-usb-devel] hanging bug with ohci-isp1362

2004-11-26 Thread Lothar Wassmann
'm using virtual addresses for any of these. > I didn't change that aspect, at any rate. > So your architecture has virtual == real addresses for main memory? Lothar Wassmann --- SF email is sponsored by - The IT Product Guid

Re: [linux-usb-devel] hanging bug with ohci-isp1362

2004-11-26 Thread Lothar Wassmann
9} > What's the value of td->hwNextTD? Since you are oviously using virtual addresses in hwNextED (according to your hexlified dbg output), I suspect that hwNextTD also is a virtual address in which case dma_to_td() cannot return any reasonable result. Lothar Wassmann

[linux-usb-devel] Re: ISP1362 driver - write_reg32 & drop_all_ptds

2004-11-25 Thread Lothar Wassmann
anyway. It's some leftovers of debugging. > That's too bad. I'm assuming that's because it works as well as > your customer needs it. > That's right. Lothar Wassmann --- SF email is sponsored by - The IT Pr

[linux-usb-devel] Re: ISP1362 driver - write_reg32 & drop_all_ptds

2004-11-23 Thread Lothar Wassmann
ked. > It's basically the version that is working for a customer. I only started to do some cleanup which obviously broke some things that were correct before. The problem is that I don't have time to spend on this driver at the moment. At least not at work. :( Lothar Wassmann

[linux-usb-devel] Re: dma_to_virt usage/alternatives in ohci / isp1362 / isp1160 drivers

2004-11-23 Thread Lothar Wassmann
fields with the DMA controller which is how it is supposed to be. Lothar Wassmann --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly li

Re: [linux-usb-devel] RE: yet more on ohci-isp1362

2004-11-18 Thread Lothar Wassmann
ourse make the 116x patch apply to your then > latest driver version. > Yes, I'd like to get your patch. I hope to find some time in between projects to merge it with my code. Lothar Wassmann --- This SF.Net email is sponsored

Re: [linux-usb-devel] RE: yet more on ohci-isp1362

2004-11-17 Thread Lothar Wassmann
ml that reflects my latest changes that hopefully will help you to get things working. Unfortunately I'm working on something completely different now, so that I can't invest much time in this driver right now. :( Lothar Wassmann

[linux-usb-devel] Re: ohci-isp1362 Done & Skip Map

2004-11-15 Thread Lothar Wassmann
TDs and > emulating the behaviour of 1362 (emulate the emulation... this is > getting more and more complex!) > I think 1) is the best solution. The 1362 has some significant advantages over the 116x that I wouldn't want to sacrifice for code compatibility with the 116x. Lothar Wassmann

Re: [linux-usb-devel] more on ohci-isp1362

2004-11-10 Thread Lothar Wassmann
field wasn't being set! > This field is set by the standard OHCI driver through the function periodic_reinit() defined in ohci.h and called from hc_start(). The value written to fminterval is initialized in hc_reset(). Lothar Wassmann ---

Re: [linux-usb-devel] ohci-isp1362 without DMA

2004-10-25 Thread Lothar Wassmann
programs the controller registers instead of creating the TDs for bus master access (that we can't use directly anyway). Lothar Wassmann --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your

RE: [linux-usb-devel] ohci-isp1362 :: addr/data offsets

2004-10-20 Thread Lothar Wassmann
e/hcd-.c so that the remaining code in ohci-isp1362.c will be completely architecture independent. Lothar Wassmann --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you th

Re: [linux-usb-devel] Re: ohci-isp1362 :: addr/data offsets

2004-10-19 Thread Lothar Wassmann
0 due to > asserted hw-reset pin. Hardware reset preformed above in > the same function occurs correctly. Must this call really be > there for 1362? > hw_reset is deasserted in isp1362_start_chip() before the chip is accessed. So it should not matter that the reset is asserted again in

RE: [linux-usb-devel] ohci-isp1362 :: addr/data offsets

2004-10-19 Thread Lothar Wassmann
age, so that I wouldn't try finding a software bug when actually the hardware was misbehaving. All necessary power on reset delays etc. should be done in the platform specific hw_reset() function. Lothar Wassmann --- This SF.net email is spo

[linux-usb-devel] Re: ohci-isp1362 :: addr/data offsets

2004-10-19 Thread Lothar Wassmann
e = "isp1362-ohci", .id = 0, .num_resources = ARRAY_SIZE(ohci_isp1362_resources), .resource = ohci_isp1362_resources, .dev = { .platform_data = &ohci_1362_data,

Re: [linux-usb-devel] Re: ohci-isp1362 / ohci-isp1160 issues

2004-10-12 Thread Lothar Wassmann
e same > number (0x600) as 'RW'... And while RW is R+W masks together, why have > the same thing with another name? > REG_ACCESS_MASK can be used to isolate the access mode bits from the register specification just like REG_NO_MASK isolates the register number. Lothar Wassma

Re: [linux-usb-devel] Updated ISP1362/116x OHCI driver files

2004-10-12 Thread Lothar Wassmann
ding it. > I'm missing this attachment. There were only three attachments: usb-ohci-emu-debug usb-ohci-emu-kconfig usb-ohci-emu-rejects Lothar Wassmann --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT pr

[linux-usb-devel] Updated ISP1362/116x OHCI driver files

2004-10-11 Thread Lothar Wassmann
Hi Olav, I finally managed to incorporate your patch for the ISP116x register definitions into my sources (there should be more weekends in a week ;) and have put the updated files on the website: http://www.karo-electronics.de/index.php?id=132 Lothar Wassmann

[linux-usb-devel] Re: ohci-isp1362 / ohci-isp1160 issues

2004-10-11 Thread Lothar Wassmann
my platform it didn't make sense to use spinlocks since it isn't SMP capable. But if the driver is going to be used on SMP capable platforms too, it doesn't hurt to use spinlocks generally. Lothar Wassmann --- This SF.net ema

Re: [linux-usb-devel] ohci-isp1362 compile trouble - missing implicit declarations

2004-10-08 Thread Lothar Wassmann
ci_dbg() calls. Lothar Wassmann --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to fi

Re: [linux-usb-devel] RE: ohci-isp1362 / ohci-emu patches

2004-10-08 Thread Lothar Wassmann
hci register accesses from readl/writel() instructions to using macros that provide the possibility to emulate registers that are not supported by the hardware. The 2.6.8 code directly wrote the hardware registers for every 'case' of the switch() statement. T

Re: [linux-usb-devel] OHCI driver for SL811HS chip

2004-10-07 Thread Lothar Wassmann
,v) ohci_write_reg(hc, fminterval, v) #define ohci_write_fmremaining(hc,v)ohci_write_reg(hc, fmremaining, v) #define ohci_write_fmnumber(hc,v) ohci_write_reg(hc, fmnumber, v) #define ohci_write_periodicstart(hc,v) ohci_write_reg(hc, periodicstart, v) #de

[linux-usb-devel] Re: OHCI driver for ISP1362 / ISP116x chip

2004-10-05 Thread Lothar Wassmann
es. You can find the current state of my work on: http://www.karo-electronics.de/132.0.html I've got so far, that the driver recognises and works with a mouse and recognises an SD card reader, but fails to read data from the SD card. Lothar Wassmann --

Re: [linux-usb-devel] hc_sl811 driver

2004-09-29 Thread Lothar Wassmann
sent out the code and already modified my local sources accordingly. Lothar Wassmann --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opi

Re: [linux-usb-devel] IO ports and memory mapping for the ISP1160 (was: OHCI-SL811 driver)

2004-09-16 Thread Lothar Wassmann
readw/writew fucntions??? > Switching from read*/write* to in*/out* is just a matter of redefining the basic access macros *_WRITE_ADDR, *_READ_DATA16 and *_READ_DATA32. Lothar Wassmann --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be

Re: [linux-usb-devel] OHCI driver for ISP1362 chip

2004-09-14 Thread Lothar Wassmann
s)) | PTD_LAST_ISO(last) | PTD_SPD(spd) | PTD_MPS_H(mps); over: PTD_SET_EP(ptd, ed_en(ed_flags)); PTD_SET_LAST_ISO(ptd, last); PTD_SET_SPD(ptd, spd); ... But we can also add the macros for setting individual fields of a PTD header. Lothar Wassmann ---

Re: [linux-usb-devel] OHCI driver for ISP1362 / 1160 chip

2004-09-13 Thread Lothar Wassmann
of what's going on. > > This is part of a project at work, so I can spend quite a bit of time > on it. Instead of working on my own, can I do anything to work with > you guys on this? > What platform are you using? Lothar Wassmann -

Re: [linux-usb-devel] OHCI driver for SL811HS chip

2004-09-13 Thread Lothar Wassmann
ld have a look at drivers/usb/core/hcd-pci.c. That's where part of my code in ohci-sl811.c comes from. ;) Lothar Wassmann --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FRE

Re: [linux-usb-devel] OHCI driver for SL811HS chip

2004-09-13 Thread Lothar Wassmann
IT 0' takes care of this - fixed some typos - the read/write_buffer function takes care of buffer alignment and should handle leading/trailing bytes correctly. At least on the 1362 that has "Direct Adress" mode to access the internal buffers. I also fixed some bugs in the SL811 code

RE: [linux-usb-devel] RE: isp1161 ISOC timeout problems

2004-09-09 Thread Lothar Wassmann
upt when reenabling interrupts at the end of the handler. Lothar Wassmann --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://a

Re: [linux-usb-devel] OHCI driver for SL811HS chip

2004-09-09 Thread Lothar Wassmann
n this through all the "usbtest" code, and seen > that it behaves OK for the transfer types you support? (And > fails cleanly for ISO.) > Not yet. I only recently figured out how to use the framework. I'll do it as soon as I find some time for

RE: [linux-usb-devel] RE: isp1161 ISOC timeout problems

2004-09-09 Thread Lothar Wassmann
4ns for PXA270 (from "PXA270 Electrical, Mechanical and Thermal Spec.") Lothar Wassmann --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic

Re: [linux-usb-devel] Re: isp1160 driver for 2.6 kernel

2004-09-07 Thread Lothar Wassmann
t have released my kernel patches to the public. Now I'm working on a driver for the ISP1362 which should be the same as the 1160 wrt the host controller funcionality. So, maybe we should join our efforts. Lothar Wassmann --- This SF.Net email

[linux-usb-devel] OHCI driver for SL811HS chip

2004-09-07 Thread Lothar Wassmann
ader, WLAN adapter,... Lothar Wassmann ohci-emu.patch.gz Description: Binary data

[linux-usb-devel] several bugs in ohci-hub.c and ohci-q.c

2004-09-07 Thread Lothar Wassmann
same size as the original operands! + */ +#define tick_before(t1,t2) ((s16)(((s16)(t1)) - ((s16)(t2))) < 0) /* there are some urbs/eds to unlink; called in_irq(), with HCD locked */ static void --- end of patch --- Lothar Wassmann --- T