> I'm working with ISP1362 on some PPC405EP-based embedded
> platforms.
..
> I found several threads in this mailing list about this chip, but
> it seems nobody works with Philips software
>
(http://www.semiconductors.philips.com/acrobat/usermanuals/UM10012_2.pdf).
> Are there particular reasons t
> I'm still waiting
> for the
> response from Philips about this point. As soon as I get it,
> we'll decide
> what to do. So far we have two options:
>
> 1) start from the driver for 116x and add support for 1362 as
> described here:
> http://sourceforge.net/mailarchive/message.php?msg_id=1088026
> is there any work done to port isp1362 full drivers for 2.6
> kernels?
>
> are there any hints for porting usb drivers for 2.6 series (i'm
> using
> 2.6.11)
> a lot of defines has gone.., structures have been changed
> there are even hard differences between 2.6.7 an 2.6.11 ...
>
> i've j
m_device_register( &isp1362_hcd_device );
if ( 0 != ret_val )
{
printk( KERN_NOTICE "--- ERR %d: Couldn't register the ISP1362 platform device.\r\n", ret_val);
}
else
{
printk( KERN_NOTICE "--- Registered the ISP1362 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.
Aaah, I see. Thanks, I put that in.
However, I'm still having trouble. Perhaps you have an idea?
I can't seem to get th
--- Robin Farine <[EMAIL PROTECTED]> wrote:
> On Tuesday 19 April 2005 15.52, Ian Campbell wrote:
>
> > I was seeing this problem on a PXA255 with an isp1160. It went
> > away when I corrected the H_WAKEUP pin to be pulled in the
> > right direction, I can't remember if it needs to be pulled up
>
Hi. I'm having some trouble with your driver, and there's parts I
don't understand. The one I'm asking about this time, is: Where is
XFERCTR being set? The below code snippet mentions assuming it's
set up, but I can't find the code that actually sets it up!
// use readsw/writesw to access the f
Hey. I nearly have this driver working (I hope), and I wanted to
give you some feedback so far on what I needed to do to get it into
my kernel.
I'm using a Sharp LH7A40x SoC, on my own custom board. This is
using the Philips ISP1362 USB-OTG controller, but I'm only using it
for host capability.
Hello again. I'm having trouble with the isp1362-hcd driver, and
any insights (or tips on how to debug) would be greatly
appreciated.
I have an 'ellisys USB Tracker', so I can take a look at the
traffic on the bus. With the isp1362-hcd driver the way I have it
right now, a bunch of the GetDescri
> > I used the define 'USE_32BIT' to 0.
> > Isn't the ISP1362 16-bit only? You can do 32-bit accesses on
> > the 16-bit bus, but then you violate the (fussy) timing for
> > sure!
> >
> That depends on the capabilities of the processors memory
> interface. At least on PXA you can program the me
--- Lothar Wassmann <[EMAIL PROTECTED]> wrote:
> Hi Michael,
>
> Michael writes:
> > I would disagree. I added a printk at the top of the
> > isp1362_irq function, as you can see in the bootup messages.
> > However, it doesn't show up with the "nob
> > No, I suppose I don't have a special reason. I'm running my
> > kernel without any modules at all, so I was sticking to that.
> > I have it automated to be easy enough to boot with a new
> > kernel. (As easy as transferring a new module over and trying
> > it out).
> >
> I'm running my test
Hi.
I'm pleased to announce that I've got my driver working! I was
able yesterday to attach a USB-network device, and get it onto the
network, and use telnet! The ohci-isp1362 driver didn't get me
that far.
That's encouraging, and I think that I'll likely be able to write
reliably to a flash driv
> Thanks for this clearing int_edge_triggered has made the
> interrupts
> appear, but unfortunately now I hit a 'BUG_ON' in isp1362_irq,
>
> 1089:spin_lock(&isp1362_hcd->lock);
> 1090:
> 1091:BUG_ON(isp1362_hcd->irq_active++);
> 1092:
> 1093:isp1362_write_reg16(isp1362_hc
--- Olav Kongas <[EMAIL PROTECTED]> wrote:
>
> On Thu, 26 May 2005, Wolfgang [utf-8] Mües wrote:
> > On Thursday 26 May 2005 08:10, Olav Kongas wrote:
> > > Philips:
> > > isp1362, full speed, host driver available (I think both
> > > with and without DMA versions, see list archives)
> >
> > H
--- Bill Gatliff <[EMAIL PROTECTED]> wrote:
> Guys:
>
>
>
> I'm trying to use an isp1161 on a PXA255-based board. The
> isp1161 is tied to CS5, with A1 tied to the isp1161's A0 pin
> and A2 tied to the isp1161's A1 pin. I'm using NDELAY.
>
> My resources look like this:
>
> static struct
--- David Kind <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We are currently designing the Philips ISP1161 USB chip onto our
> boards.
> The intention is to use Linux 2.6 on a ppc 85xx - we already have
> U-boot
> running :)
>
> However, we are concerned at about the stability of the ISP1161
> driver.
Hi.
This is a small issue, but it's an error nonetheless.
(I'm not sure how important this Power-on-to-power-good-time is)
In ohci-isp1362.c, this line:
#define RH_A_POTPGT_(n) ((n) & 0xff << 24)
needs to be changed to this:
#define RH_A_POTPGT_(n) (((n) & 0xff) << 24)
Mike
Is it just me, or are we getting more and more spam recently?
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.c
> > Do you off-hand know why the HCD needs to receive these
> > interrupts?
> > SOFs happen all the time, but you don't need to react to them,
> > do you?
>
> The driver must stay in sync with SOFs to be able to ensure
> timely processing of iso and int transfers.
>
Aren't there INTL interrupts
Hi. I'm still working on getting my USB working with the
OHCI-ISP1362 driver. Here's one problem I found that was stopping
me.
There's a field in the Frame Interval register (reg HcFmInterval,
0x0D) called FSLargestDataPacket (FSMPS). It specifies the largest
amount of data in bits that can be
>
> Sounds like there are still delays missing.
>
Yeah, it does. A 1 micro-second delay should do it, right?
I've also run into trouble with how picky the chip is. For
instance, the chip select and read signal must be deasserted
between reads. (see Fig. 31, pg 137 of the ISP1362 manual) If I
27;s used.
+
+// Detect the board revision
+int board_rev = 7 - ((GPIO_PA_PIND & 0x70) >> 4);
+*/
+
+// Add our platform devices defined above
+(void) platform_add_devices( oscar_platform_devices,
ARRAY_SIZE(oscar_platform_devices) );
+}
+
MACHINE_START (OS
I don't think I can comment on your endianness issue.
> I now have enumeration working, but it now hangs when getting the
> device
> descriptor. Hopefully I can provide you some feedback soon.
>
You know.. I'm getting further now in my enumeration, and it also
hangs when getting the device de
Hi. I'm trying to use the changes in your latest driver, but there
are two bigger issues I've run into.
1. It doesn't seem to include the functions 'drop_all_ptds' and
'drop_ptds_for_td', which are necessary in order to compile.
2. The read/write_data32 calls seem to me to be wrong, as they only
Hello again.
> > 1. It doesn't seem to include the functions 'drop_all_ptds' and
> > 'drop_ptds_for_td', which are necessary in order to compile.
> >
> Grrr. I renamed the function to 'clear_ptd_queue' but obviously
> missed to change some calls in ohci-isp1362-regs.h.
Thanks, that's good to kno
Hi. I've incorporated your changes, and it seems to work much
better. I can enumerate a variety of devices, and even read from a
USB flash drive!
However, I'm running into a bug when I try to write to it.
I'm still trying to decipher it all, but if you have any ideas,
they are welcome.
Thanks!
> I can debug it, and it seems stuck in this loop:
> (ohci-isp1362-emu.c)
>
> while (td != NULL && ED_TAILP(ed) != td->td_dma) {
> u32 td_flags = get_hwinfo(td);
> DPRINTK("MWMDEBUG: td_flags = %ul\n", td_flags);
> if (TD_CC_GET(td_flags) == TD_NOTACCESSED) {
> *edp = ed;
> break;
>
--- Lothar Wassmann <[EMAIL PROTECTED]> wrote:
> Hi,
> > However, I'm running into a bug when I try to write to it.
> > I'm still trying to decipher it all, but if you have any ideas,
> > they are welcome.
> >
> > Thanks!
> > Mike
> >
[...]
> What's the value of td->hwNextTD? Since you are ovi
Hello again.
> On Thu, 25 Nov 2004, Michael wrote:
> >
> > Sorry, a quick correction. The DPRINTK line in there wasn't
> > used for the output I included. In fact, with that debug line
> > there, it doesn't enumerate or send any USB traffic at all!
&g
> I adding printing out of the td_flags, and it seems that every
> time
> that it gets the condition code of 0xA (which is reserved in the
> OHCI spec, but is defined as TD_BUSY in ohci-isp1362-emu.c), it
> gets stuck in this loop.
>
> So it seems that it doesn't handle the busy condition. It lo
> Hi Michael,
>
> Michael wrote:
> > Hi. Here's some more data dumps:
> >
[...]
> >
> > I'm not sure that I'm using virtual addresses for any of these.
> > I didn't change that aspect, at any rate.
> >
> So your architect
he amount of
> the debug stuff printed. With less printable stuff, the
> device just keeps responding with NAK-s at some point
> indicating that the change of the sequence was crucial. The
> low-level usb bus traffic seems normal.
>
> Michael, what happens if you print out m
Hello ISP1362/1160/.. mates.
Have any of you ran into this error message:?
" update_td_status: TD c115d040 ERROR 3 TD_CC_DATATOGGLEM
Retiring TD c115d040 ED c115c080 info 00401102 with CC=3 #887b
retire_td: ED c115c080 (TD c115d040) Halted due to error: 3 "
I thought I could read from a USB f
Hi. I am trying to get the ohci-isp1362 driver working, and I feel
like I am almost there. Here's my situation:
The only thing I'm using it for right now is to transfer files to
and from a flash drive. I can enumerate fine, and it seems I can
list files and directories just fine too. I can wri
> hi
> i download the patch file from
> http://www.boundarydevices.com/usbpatch/
> and patch it to my kernel
> my hardware is pxa255-base and isp1161 use CS5
[...]
> but when i try a usb device(card reader)
> kernel shows:
>
> -
> / # USB HC dev alloc 384 b
--- Lothar Wassmann <[EMAIL PROTECTED]> wrote:
> 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
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
caused by the BUG_ON macro..
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
> 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
--- Lesha Shervashidze <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have the problem with USB2 host controller Fhilips
> ISP 1561BM using Coldfire 5485. I use Linux OHCI
> driver and I have the address error if I try to plug
> any device:
>
Hrm. Which version of the kernel are you using?
I just d
> > In summary, I have tried hard to convince the world and
> > myself that somebody else is guilty of this error :) Thanks
> > for your help.
>
> No problem, thanks for taking the time to investigate!
>
I just wanted to add my thanks as well. Thanks Olav! (a bunch)
It sounds to me like it's
--- Olav Kongas <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, 1 Nov 2004, xemc wrote:
>
> > > ohci_isp1362_interrupt: Read 0001 from HCuPINT
> > > ohci_isp1362_interrupt: Acknowledging 0001
> >
> > And this keeps looping. I continually get interrupts due to
> SOFs
> > (Should this even happen?), bu
working). The idea of restarting the chip is taken from
public Darwin code.
Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
---
The OHCI driver uses inconsistent code formatting. I tried to stay with
the used style where I modified functions while using Doc/CodingStyle
for new functions.
lost_power again but disables CONFIG_PM specific code in it
when CONFIG_PM isn't defined. It seems to work for me with and without
CONFIG_PM, but I have to confess I might not know enough about Linux'
USB core. Is it better now?
Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
5ec] kthread+0x4c/0x88
[ 76.503656] [dff13ff0] [c001433c] kernel_thread+0x44/0x60
[ 76.504367] Instruction dump:
[ 76.504960] 7fc3f378 4bffb645 387f0040 3881 38a00001 38c0 4bd66b1d
813f005c
[ 76.505905] 480c 4bdc5021 813d0410 3ba9fbf0 <801d0410> 2f80 419e0008
7c00022c
eyboard / Trackpad as
/class/input/input18 on usb-0001:10:15.1-2
(Actually, I added some code to trigger the error handling code, reliably
reproducing it otherwise is impossible.)
Thanks,
Michael
-
This SF.net email is sp
out and drop the
changes on usb_root_hub_lost_power for CONFIG_PM?
Greets,
Michael
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No li
usb 5-5: new high speed USB device using ehci_hcd and address 4
usb 5-5: device descriptor read/64, error -71
usb 5-5: device descriptor read/64, error -71
usb 5-5: new high speed USB device using ehci_hcd and address 5
usb 5-5: device descriptor read/all, error -71
usb 5-5: new high speed USB devi
uled again. This patch fixes that.
> Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
Acked-by: Michael Hanselmann <[EMAIL PROTECTED]>
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.n
). Sending this mail
because the log message told me to :-)
I'm not a member of this list.
--
Michael Lindner
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Disco
Randy.Dunlap wrote:
On Mon, 18 Apr 2005 11:15:50 -0500 Stephen Morgan wrote:
| Hello all,
|
| I'm converting a USB driver for Linux 2.4.20-8 to 2.6.9-1.667 and have found
| that the __FILE__ macro is now giving me the full path of the driver source.
| In 2.4, I was just getting the file name. Lik
Randy.Dunlap wrote:
On Mon, 18 Apr 2005 14:51:38 -0500 Stephen Morgan wrote:
[]
| Thanks Randy. So, is __FILE__ deprecated usage now? I know it was
| used extensively at least in 2.4 (As in the usb-skeleton.c dbg macro.)
I don't know that __FILE__ is deprecated and I didn't say that.
It works, it
as the mapping is quite close. Also the version of the remote
is a UIA-11 which doesn't require a programming download to work. There
is a UIA-10 version which is an older version which does.
Enjoy,
Michael Downey
Signed-off-by: [EMAIL PROTECTED]
I'm using Thunderbird and can't
It looks like my last email got messed up even though I spent 15 minutes
making sure it was correct. I'm attaching the patch as it looks like
Thunderbird does an appropriate job attaching text. If this isn't
satisfactory please let me know and I'll try to dig up something else.
of doing that let me know.
Also I have only explicitly size the variables in the structures that
need to have explicit sizes. All other variables are don't care
situations I believe. If I am still in error then please let me know.
Michael Downey
Zymeta Corporation
Signed-off-by: [EMAIL PRO
It looks like I forgot to disable the debug messages in my last patch:
debug = 1 should be debug = 0. I will resend the driver after some
people get a chance to look at the rest of the code.
Sorry about that,
Michael Downey
Zymeta Corporation
what the CS8900a code is doing as
this has the same exact set of issues.
Michael
P.S. This means it working though?
At 03:29 PM 6/29/2005, Bill Gatliff wrote:
Guys:
Odd odd odd. :^)
The only combination which seems to work for me is this:
static struct isp116x_platform
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 interrupt line before you
> re-enable the GPIO interrupt. That way if the device is asking
>
indows live" nonsense as after all it seems to use HID to
transmit dialing information to the PC and Audio for the telephony.
Regards
Michael
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
--
nks and sorry for the probably wrong error report :-)
Regards
Michael
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
Bus 001 Device 012: ID 0471:0830 Philips
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB
bCountryCode0 Not supported
> bNumDescriptorscannot read device status, Broken pipe (32)
> 1
> bDescriptorType34 Report
> wDescriptorLength2449
> Report Descriptors:
> ** UNAVAILABLE **
Regard
Hello,
The below patch proposes to use USB defines (defined in linux/hid.h) instead
of just plain numbers in the USB_INTERFACE_INFO statements.
Isn't this cleaner and more explicit?
I know that these numbers will not change, of course...
What do you think?
Cheers,
Mi
x27; undeclared here (not in a function)
> ...
> make[4]: *** [drivers/usb/host/ohci-hcd.o] Error 1
>
> <-- snip -->
>
>
> cu
> Adrian
>
--
Greetings Michael.
-
Take Surveys. Earn Cash.
On Monday 05 March 2007 11:49, Michael Buesch wrote:
> On Monday 05 March 2007 02:47, Adrian Bunk wrote:
> > On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.20-mm2:
> > >...
> > >
On Monday 05 March 2007 11:57, Michael Buesch wrote:
> > > CC drivers/usb/host/ohci-hcd.o
> > > In file included from
> > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931:
> > > /home/bunk/linux/kernel-2.6/linux-2.6.21
On Monday 05 March 2007 19:42, David Brownell wrote:
> On Monday 05 March 2007 3:26 am, Michael Buesch wrote:
>
> > > Actually, it seems like I will run into other kinds of nasty problems
> > > due to stupid design of the HCD code. The OHCI code #includes
> > >
Hi,
I'm trying to understand how the USB Mass Storage Device
works in 2.6. Specifically 2.6.14. I see a fair amount of
churn in this subsystem.
My principle concern/question is how does data from a file
on the filesystem get transported to a memory stick? I
have dumped info at many stages and
between 2.6.9, 2.6.14. AFter 2.6.14
there is very little change. I have yet to find a decent
source that may describe why these changes were made and
hence wonder if different versions may cause
incompatibility with this example driver?
Thanks,
Mike.
--- Alan Stern <[EMAIL PROTECTED]> wro
Thanks Alan,
It is good to get some feedback on how the buffer
manipulation should work. I appreciate you taking the
time.
>
> Did you take care about checking byte-endian issues?
>
Yep, I didn't take enough care. I thought I had, but I
have just found the URB transfer buffer is fragmented i
Hi
The basic problem that I'm having is that Playstation controllers connected
via a USB adapter are not working. I've posted on usb-users and was advised
to post here.
The USB adapter supports 2 controllers (players 1 and 2). When plugged in,
it is detected (appropriate kernel modules are l
EMAIL PROTECTED]>
+#define USB_VENDOR_ID_HP 0x03f0
+#define USB_DEVICE_ID_HP_USBHUB_KB 0x020c
Oh for crying out loud. It's exactly the same keyboard! Look at this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55878
The bug was filed in 2001, for 2.4.9 kernel. I
at distro and kernel version are you using -- can you mail me
your kernel config file?
Michael
From: Andrew Fuller <[EMAIL PROTECTED]>
To: linux-usb-devel@lists.sourceforge.net, Michael Alladin
<[EMAIL PROTECTED]>
Subject: Wisegroup MP-8866 Dual USB Joypad
Date: Sat, 21 Jan 2006 11:
special in its init scripts.
Michael
From: Andrew Fuller <[EMAIL PROTECTED]>
To: Michael Alladin <[EMAIL PROTECTED]>
CC: linux-usb-devel@lists.sourceforge.net
Subject: Re: Wisegroup MP-8866 Dual USB Joypad
Date: Tue, 7 Feb 2006 19:45:11 -0500
Sorry it took me so long to get back you
only one device node is
created (js0), but there should be two, right? (And no, the SDL library
patch that handles two joysticks via one device is just not cool).
Michael
From: "Andrew Fuller" <[EMAIL PROTECTED]>
To: "David Brownell" <[EMAIL PROTECTED]>
CC: lin
n usb-:00:10.2-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
From: "Andrew Fuller" <[EMAIL PROTECTED]>
To: "Alan Stern" <[EMAIL PROTECTED]>, "Michael Alladin"
<[EMAIL PROTECTED]>, &q
he
stage on the message back to 0 which is what we want.
So the change probably should be something like:
} else {
err("%s - Error in message, invalid toggle.\n", __FUNCTION__);
+ message->stage = 0;
+ return;
}
Tha
Greg KH wrote:
>On Mon, Mar 27, 2006 at 09:05:38AM -0700, Michael Downey wrote:
>
>
>>Adrian Bunk wrote:
>>
>>
>>
>>>gcc reported the following:
>>>
>>><-- snip -->
>>>
>>>...
>>>
sing hiddev then my
only other option is implementing the whole thing using just libusb.
Any help would be appreciated,
Michael Downey
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applicat
erate 11 events per insert instead of 338. This would
mean making changes to the file access structures which would likely
break things for other people.
If no one has issues I will submit a patch to just up the
HIDDEV_BUFFER_SIZE to 512 from 64.
Michael D
Vojtech Pavlik wrote:
>On Mon, Apr 10, 2006 at 05:03:21PM -0700, Greg KH wrote:
>
>
>
>>On Mon, Apr 10, 2006 at 03:08:50PM -0600, Michael Downey wrote:
>>
>>
>>>I am currently looking at using a MegTek USB insertion reader and I have
>>>run i
Vojtech Pavlik wrote:
>On Tue, Apr 11, 2006 at 08:52:17AM -0600, Michael Downey wrote:
>
>
>
>>>The reason is that it was originally intended for devices which don't
>>>issue huge numbers of reports in one go, and 64 was supposed to be
>>>'la
org
The output I get when running make is attached below.
Regards,
Michael
PS: I first posted this in usenet comp.os.linux.hardware and was redirected to
send it to linux-usb-devel and lkml. Please tell me when I'm wrong.
Output of make:
[EMAIL PROTECTED] ~/mcs7830FC4Ver1.0.0.1 $ LC_ALL=
Am Dienstag 02 Mai 2006 22:40 schrieb Ioan Ionita:
> On 5/2/06, Michael Helmling <[EMAIL PROTECTED]> wrote:
> > Thank you very much for the immediate answer.
> > I applied the patch - well, I had to do this manually, for some reason, I
> > assume bad formatting in
On Wednesday 03 May 2006 00:09, David Brownell wrote:
> On Tuesday 02 May 2006 11:02 am, Michael Helmling wrote:
> > Hi all,
> >
> > I bought an USB-Ethernet adaptor from delock (www.delock.de) and found it
was
> > not supported by linux from the vendor. So I play
On Wednesday 03 May 2006 07:29, David Brownell wrote:
> On Tuesday 02 May 2006 10:06 pm, Michael Helmling wrote:
>
> They just hacked "usbnet". There are huge chunks of code, and comments,
> that are clearly identical. At least half of the "moschip" driver.
&g
On Wednesday 03 May 2006 07:29, David Brownell wrote:
> On Tuesday 02 May 2006 10:06 pm, Michael Helmling wrote:
>
> They just hacked "usbnet". There are huge chunks of code, and comments,
> that are clearly identical. At least half of the "moschip" driver.
&g
On Wednesday 03 May 2006 17:31, Andrey Panin wrote:
> > What he
> > should do would be to create a moschip.c that uses usbnet as a support
> > module - just like asix.c does. In this file, he can have his sole
> > Copyright attribution and not have to worry about following
> > changes/updates to u
Hi Markus,
I'm sorry but your attachment has 0kb size. :(
On Friday 05 May 2006 14:54, Markus Rechberger wrote:
> Hi Michael,
>
> I mailed you the complete package it compiled fine but I'm also unable to
> test since I don't have such a device either
> I shoul
ework then. Fixing the copyrights shouldn't be such a
> problem there :)
What about the file you tried to send me? It had 0kb size, so I couldn't test
it.
Michael
>
> Markus
>
> On 6 May 2006 19:23:11 -0400, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > &g
This is a driver to control the brightness of an Apple Cinema Display
over USB. It updates the local brightness value if the user presses a
button on the display.
Please apply to -mm for testing if nothing major is broken.
Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
---
diff
Hello Oliver
On Fri, May 26, 2006 at 11:29:14AM +0200, Oliver Neukum wrote:
> > + char buffer[2];
> DMA on the stack. You must not do this. Allocate the buffer with kmalloc.
This and the other errors are fixed in the patch below.
Thanks,
Michael
---
diff -Nrup --exclude-f
ig USB_APPLEDISPLAY
> I have such a display - shall try to remember to test the driver, thanks.
Thanks!
Are complete patches okay for you or would you like to have diffes
against the earlier patch?
Greets,
Michael
---
diff -Nrup --exclude-from linux-exclude-from
linux-2.6.17-rc5.orig/driver
Unable to get an ipaq running GPE Linux to connect to intel linux box.
I'm running kernel version: 2.6.17-rc6
When I plug in the ipaq, I get the following log messages.
The ipaq does not show up in lsusb after this.
The ipaq works fine on 2 other systems which are both running 2.4 series
kernels.
After doing some digging with regards to my original problem (PSX Dual Pad
adapter not functioning) I have noticed a couple of things.
1. Even though it's a DUAL Adapter, only ONE device node, /dev/input/js0 is
created. No matter how many "joysticks" I plug in i.e. 0, 1 or 2.
2. After turnin
ISD300 gets detected correctly you can plug it in and out on the
running system without problems.
Tested with 3 different motherboards (OHCI and also UHCI), always the same
result.
Under w2k this problem does not occur.
Has somebody else experienced a similar problem with ISD300?
Michael
On Tue, 19 Nov 2002 20:53:44 -0800
[EMAIL PROTECTED] wrote:
> linux-usb-devel -- confirmation of subscription -- request 454153
>
> We have received a request from 210.172.124.112 for subscription of
> your email address, <[EMAIL PROTECTED]>, to the
> [EMAIL PROTECTED] mailing list. To confirm t
You do not have to keep the rate of 1 ms exactly. Just do not allow idle
periods of > 3m. It will suspend devices. Never worked with SL part. But if
you want to byte-bang USB you need at least 6MIPS MCU for low-speed and
48MIPS for full speed. Well, and some external logic of course. Worked for
m
48 MIPS x 8. To do the byte-bang reduce the speed
of MCU by 8. Probably for SL with internal buffers you do not need speed
this high.
I have no idea what you are trying to interface to USB. But anything below
40 MIPS is good only for keyboards and mice. Printers, cameras and flash
disks need mo
->ep_bInterval = ep_int->bInterval;
> > + if (ep_int) {
> > + ss->ep_int = ep_int->bEndpointAddress &
> > + USB_ENDPOINT_NUMBER_MASK;
> > + ss->ep_bInterval = ep_int-
1 - 100 of 192 matches
Mail list logo
