On Feb 28, 2011, at 5:34 PM, Jarod Wilson wrote:
> On Feb 17, 2011, at 6:46 AM, Lucian Muresan wrote:
>
>> On 09.02.2011 06:19, Jarod Wilson wrote:
>> [...]
>>> Looks like bInterfaceNumber == 2 on this device. The patch to handle this
>>> similar to the conexant polaris devices should be pretty t
On Feb 17, 2011, at 6:46 AM, Lucian Muresan wrote:
> On 09.02.2011 06:19, Jarod Wilson wrote:
> [...]
>> Looks like bInterfaceNumber == 2 on this device. The patch to handle this
>> similar to the conexant polaris devices should be pretty trivial. I'll
>> try to get something together tomorrow.
>
On 09.02.2011 06:19, Jarod Wilson wrote:
[...]
> Looks like bInterfaceNumber == 2 on this device. The patch to handle this
> similar to the conexant polaris devices should be pretty trivial. I'll
> try to get something together tomorrow.
Hi,
any news on this one?
Regards,
Lucian
--
To unsubscrib
On Feb 8, 2011, at 8:38 PM, Lucian Muresan wrote:
> On 09.01.2011 18:36, Patrick Boettcher wrote:
>> Hi Jarod,
>>
>> I'm using an MultiCard-reader which exposes itself like shown below.
>>
>> It is falsly claimed by the mceusb-driver from (2.6.36 from debian-
>> experimental) .
Bah. First up, a
On 09.01.2011 18:36, Patrick Boettcher wrote:
> Hi Jarod,
>
> I'm using an MultiCard-reader which exposes itself like shown below.
>
> It is falsly claimed by the mceusb-driver from (2.6.36 from debian-
> experimental) .
Hi there,
I also bought a similar Multi-Cardreader, which also comes wit
Hi Jarod,
I'm using an MultiCard-reader which exposes itself like shown below.
It is falsly claimed by the mceusb-driver from (2.6.36 from debian-
experimental) .
Would be good to create an exception for this one if possible. Let me know if
you need more information or if you want me to take o
