Am Sonntag, 7. Juni 2009 15:41:13 schrieb Alexey Klimov:
> > If not, the driver may not be 64bit clean. Which driver is affected?
>
> media/radio/radio-mr800.c
I can see no obvious 64bit problem.
> Please, also take a look in my first letter to usb and v4l mail lists
> from May 27.
Please resen
Hello,
On Sun, Jun 7, 2009 at 1:07 AM, Oliver Neukum wrote:
> Am Freitag, 5. Juni 2009 00:43:04 schrieb Alexey Klimov:
>> Is there any ideas about different behaviour of device on 32- and
>> 64-bit platforms with the same usb bulk messages?
>> Any input is welcome.
>
> Are you running a 32 bit use
Am Freitag, 5. Juni 2009 00:43:04 schrieb Alexey Klimov:
> Is there any ideas about different behaviour of device on 32- and
> 64-bit platforms with the same usb bulk messages?
> Any input is welcome.
Are you running a 32 bit userland? If so, ioctls could be critical.
If not, the driver may not be
On Fri, Jun 5, 2009 at 2:53 AM, Greg KH wrote:
> On Fri, Jun 05, 2009 at 02:43:04AM +0400, Alexey Klimov wrote:
>> Is there any ideas about different behaviour of device on 32- and
>> 64-bit platforms with the same usb bulk messages?
>
> No, there should be no difference.
>
> Have you run usbmon to
On Fri, Jun 05, 2009 at 02:43:04AM +0400, Alexey Klimov wrote:
> Is there any ideas about different behaviour of device on 32- and
> 64-bit platforms with the same usb bulk messages?
No, there should be no difference.
Have you run usbmon to look at the data on the wire?
thanks,
greg k-h
--
To u
Is there any ideas about different behaviour of device on 32- and
64-bit platforms with the same usb bulk messages?
Any input is welcome.
On Wed, May 27, 2009 at 9:51 PM, Alexey Klimov wrote:
[...]
> So, the same messages to device works fine with radio on 32bit machine
> and nothing on 64bit ma
Hello,
Doing some improvements in media/radio/radio-mr800.c i see very
strange situation.
I made simple patch that removed usb_amradio_open function. There is
no need in this function (no need to start/set frequency radio in open
procedure, and also removed lock/unlock_kernel() calls).
Here is thi
