On Wed, Jun 04, 2014 at 01:05:03PM -0400, Mike Remski wrote:
> On 06/04/2014 12:00 PM, Johan Hovold wrote:
> > On Wed, Jun 04, 2014 at 11:41:47AM -0400, Mike Remski wrote:
> >> Ok, had a chance to try the cdc-acm; yes it's the ancient one that is
> >> in the base install of CentOS 6.4 (2.6.32-71.2
On 06/04/2014 12:00 PM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 11:41:47AM -0400, Mike Remski wrote:
Ok, had a chance to try the cdc-acm; yes it's the ancient one that is
in the base install of CentOS 6.4 (2.6.32-71.29.1 centos patched). I'm
hitting something similar; I noticed there wher
On 06/04/2014 12:00 PM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 11:41:47AM -0400, Mike Remski wrote:
Ok, had a chance to try the cdc-acm; yes it's the ancient one that is
in the base install of CentOS 6.4 (2.6.32-71.29.1 centos patched). I'm
hitting something similar; I noticed there wher
On Wed, Jun 04, 2014 at 11:41:47AM -0400, Mike Remski wrote:
> Ok, had a chance to try the cdc-acm; yes it's the ancient one that is
> in the base install of CentOS 6.4 (2.6.32-71.29.1 centos patched). I'm
> hitting something similar; I noticed there where a few commits for NULL
> pointer der
On 06/04/2014 11:09 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:55:28AM -0400, Mike Remski wrote:
On 06/04/2014 10:52 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
On 06/04/2014 10:19 AM, Johan Hovold wrote:
>From 4ddea3a573b8c15beefb67bc35c440850
On 06/04/2014 11:09 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:55:28AM -0400, Mike Remski wrote:
On 06/04/2014 10:52 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
On 06/04/2014 10:19 AM, Johan Hovold wrote:
>From 4ddea3a573b8c15beefb67bc35c440850
On Wed, Jun 04, 2014 at 10:55:28AM -0400, Mike Remski wrote:
> On 06/04/2014 10:52 AM, Johan Hovold wrote:
> > On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
> >> On 06/04/2014 10:19 AM, Johan Hovold wrote:
> >>> >From 4ddea3a573b8c15beefb67bc35c440850063d79d Mon Sep 17 00:00:00 2001
On 06/04/2014 10:52 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
On 06/04/2014 10:19 AM, Johan Hovold wrote:
>From 4ddea3a573b8c15beefb67bc35c440850063d79d Mon Sep 17 00:00:00 2001
From: Johan Hovold
Date: Wed, 4 Jun 2014 14:09:43 +0200
Subject: [PATCH 1
On 06/04/2014 10:52 AM, Johan Hovold wrote:
On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
On 06/04/2014 10:19 AM, Johan Hovold wrote:
>From 4ddea3a573b8c15beefb67bc35c440850063d79d Mon Sep 17 00:00:00 2001
From: Johan Hovold
Date: Wed, 4 Jun 2014 14:09:43 +0200
Subject: [PATCH 1
On Wed, Jun 04, 2014 at 10:29:37AM -0400, Mike Remski wrote:
> On 06/04/2014 10:19 AM, Johan Hovold wrote:
> > >From 4ddea3a573b8c15beefb67bc35c440850063d79d Mon Sep 17 00:00:00 2001
> > From: Johan Hovold
> > Date: Wed, 4 Jun 2014 14:09:43 +0200
> > Subject: [PATCH 1/5] USB: ftdi_sio: fix null d
On 06/04/2014 10:19 AM, Johan Hovold wrote:
On Tue, Jun 03, 2014 at 06:17:33AM -0400, Mike Remski wrote:
On 06/02/2014 01:46 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -04
On Tue, Jun 03, 2014 at 06:17:33AM -0400, Mike Remski wrote:
> On 06/02/2014 01:46 PM, Johan Hovold wrote:
> > On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
> >> On 06/02/2014 12:49 PM, Johan Hovold wrote:
> >>> On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
> On 0
On 06/02/2014 01:46 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -040
On 06/02/2014 01:46 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -040
On Mon, Jun 02, 2014 at 01:11:37PM -0400, Mike Remski wrote:
> On 06/02/2014 12:49 PM, Johan Hovold wrote:
> > On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
> >> On 06/02/2014 12:20 PM, Johan Hovold wrote:
> >>> On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> On 0
On 06/02/2014 12:49 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon,
On Mon, Jun 02, 2014 at 12:24:44PM -0400, Mike Remski wrote:
> On 06/02/2014 12:20 PM, Johan Hovold wrote:
> > On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> >> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> >>> [ Please avoid top-posting. ]
> >>>
> >>> On Mon, Jun 02, 2014 at 11:16:
On 06/02/2014 12:23 PM, Greg KH wrote:
On Mon, Jun 02, 2014 at 12:09:36PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references
On 06/02/2014 12:20 PM, Johan Hovold wrote:
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross refere
On Mon, Jun 02, 2014 at 12:02:40PM -0400, Mike Remski wrote:
> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> > [ Please avoid top-posting. ]
> >
> > On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> >> Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> >> over o
On Mon, Jun 02, 2014 at 12:09:36PM -0400, Mike Remski wrote:
> On 06/02/2014 11:40 AM, Johan Hovold wrote:
> >[ Please avoid top-posting. ]
> >
> >On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> >>Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> >>over on
>
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest vers
On 06/02/2014 11:40 AM, Johan Hovold wrote:
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest vers
[ Please avoid top-posting. ]
On Mon, Jun 02, 2014 at 11:16:11AM -0400, Mike Remski wrote:
> Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
> over on
> http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
> latest version it's showing is 3.14. It appears
Thanks Johan, that's why I looked at the cross references for ftdi_sio.c
over on
http://lxr.free-electrons.com/source/drivers/usb/serial/ftdi_sio.c,
latest version it's showing is 3.14. It appears that the ftdi_sio code
is largely the same as in 2.6.32, particularly in the
ftdi_set_max_packet_
On Mon, Jun 02, 2014 at 10:25:39AM -0400, Mike Remski wrote:
> Please CC me as not subscribed to list.
> Third party device, with FTDI chip on it. Get this when plugging device
> in. Discovered in kernel 2.6.32
Wow, that kernel is ancient. Please upgrade to a more recent kernel such
as v3.14.5,
26 matches
Mail list logo