On Fri, Mar 28, 2014 at 07:27:33PM +0100, ldro...@debian.org wrote:
> > At least if
> > you can verify that it still works on an LE system.
>
> Yes your patch works on a LE system (tested on 3.2.55)
>
> Thanks!
Great, thanks for testing. I'll revisit and resend the fix in a few
days.
Johan
--
T
> At least if
> you can verify that it still works on an LE system.
Yes your patch works on a LE system (tested on 3.2.55)
Thanks!
--
Ludovic Drolez.
http://www.aopensource.com - The Android Open Source Portal
http://www.drolez.com - Personal site - Linux and Free Software
Hi Johan,
I just tested your patch on a x86 system and everything works fine.
If I find some time I'll try to find why the module crashes on arm
with debug=1.
Best regards,
--
Ludovic Drolez.
http://www.aopensource.com - The Android Open Source Portal
http://www.drolez.com
On Thu, Mar 13, 2014 at 09:40:02AM +, Ludovic wrote:
> > Did you get a chance to verify my (unmodified) patch (on BE and LE)? Are you
> > able to test it against a recent kernel on your router or are you stuck
> > with an old kernel?
>
> Hi!
>
> I've just installed a VM with a custom kernel t
> Did you get a chance to verify my (unmodified) patch (on BE and LE)? Are you
> able to test it against a recent kernel on your router or are you stuck
> with an old kernel?
Hi!
I've just installed a VM with a custom kernel to be able to test the latest
patch on LE. But for BE, I'm stuck with an
On Wed, Feb 26, 2014 at 05:01:10PM +0100, Johan Hovold wrote:
> On Tue, Feb 25, 2014 at 03:55:07PM +, Ludovic wrote:
> > At 1st the driver detected the USB key and set-up the serial ports. But when
> > trying to write I got a kernel panic on the router.
>
> Are you able to get a stack trace?
On Tue, Feb 25, 2014 at 03:55:07PM +, Ludovic wrote:
> Johan Hovold writes:
> >
> > Care to try the patch below?
> >
> > This driver could use some cleaning up so I might rework the patch
> > somewhat, but let's find the bugs first.
> >
> > Thanks,
> > Johan
> >
>
> Hi,
>
> At 1st the dr
Johan Hovold writes:
>
> Care to try the patch below?
>
> This driver could use some cleaning up so I might rework the patch
> somewhat, but let's find the bugs first.
>
> Thanks,
> Johan
>
Hi,
At 1st the driver detected the USB key and set-up the serial ports. But when
trying to write I got
[ Please do not drop recipients from your replies, that is, in this case
respond directly to me while keeping the list on CC to avoid messages
being overlooked.
Keeping some context and responding inline is also recommended. ]
On Thu, Feb 20, 2014 at 11:09:55AM +, Ludovic wrote:
> Hi
Hi !
I've tried your patch but that was not ok.
Here are the logs:
Feb 19 20:44:24 10.0.0.254 kernel: [517090.88]
drivers/usb/serial/io_ti.c: read_download_mem - @ 0 for 1
Feb 19 20:44:24 10.0.0.254 kernel: [517090.90]
drivers/usb/serial/io_ti.c: read_download_mem - @ 2 for 4
Feb 19 20:4
On Tue, Feb 18, 2014 at 08:49:17AM +, Ludovic wrote:
> Johan Hovold writes:
> > Care to test the patch below (against usb-next) on both your LE and BE
> > machines?
>
> Thanks I'll try your patch next WE.
Great.
> I've patched the code in a similar way a few days ago, but I have strange
> p
Johan Hovold writes:
> Care to test the patch below (against usb-next) on both your LE and BE
> machines?
Thanks I'll try your patch next WE.
I've patched the code in a similar way a few days ago, but I have strange
problems: I can do a write and a read, but then I have to close the serial
port o
On Thu, Feb 13, 2014 at 03:49:55PM +, Ludovic wrote:
> I've created a little libusb perl script to debug the device, and found that
> I could simulate the MIPS bug if I would send a read_download_mem address in
> LE format instead of BE, e.g.:
>
> $dev->control_msg((64 + 0 + 128), 0x92 , 0x
Hello,
I'm trying to use Edgeport sensors on my Openwrt router (Atheros MIPS CPU
with 3.3.8 kernel). It does not work and I have enabled debug output below:
Feb 11 20:28:42 10.0.0.254 kernel: [5650055.17] usb 1-1: new full-speed
USB device number 10 using ehci-platform
Feb 11 20:28:42 10.0.0.
14 matches
Mail list logo
