On Tuesday 21 June 2011 19:17:13 Luiz Gustavo S. Costa wrote:
> Hi Hans !
>
> theoretically would only do this, put the id's in the files for the udav.c
> work,
>
> but was not so, the driver did not work with these entries, simply
> could not allocate a PHY.
>
> Dmesg:
> ugen0.2: at usbus0
> u
Hi Hans !
theoretically would only do this, put the id's in the files for the udav.c work,
but was not so, the driver did not work with these entries, simply
could not allocate a PHY.
Dmesg:
ugen0.2: at usbus0
udav0: on usbus0
udav0: attaching PHYs failed
In OpenBSD working normally.
2011/6/
On Friday 17 June 2011 15:46:17 Luiz Gustavo S. Costa wrote:
> Hi all
>
> I was venturing more on the idea of running this adapter, I decided to
> test on OpenBSD 4.9
>
> OpenBSD 4.9 RELEASE is already entry for id 0x8180, equal to FreeBSD
> 9.0-CURRENT.
>
> What I did (see attached diff file) w
Hi all
I was venturing more on the idea of running this adapter, I decided to
test on OpenBSD 4.9
OpenBSD 4.9 RELEASE is already entry for id 0x8180, equal to FreeBSD
9.0-CURRENT.
What I did (see attached diff file) was to do the same, I tried to do
in freebsd, add the id of the new adapter bas
usbconfig dump_all_config_desc:
http://www.luizgustavo.pro.br/~lgcosta/jp1080/usbconfig_all_desc.txt
2011/6/10 Luiz Gustavo S. Costa :
> Hi Rick,
>
> 2011/6/10 Rick van der Zwet :
>> On 10 June 2011 14:17, Luiz Gustavo S. Costa wrote:
>>> I'm trying to add a new product id [1] to the driver udav
Hi Rick,
2011/6/10 Rick van der Zwet :
> On 10 June 2011 14:17, Luiz Gustavo S. Costa wrote:
>> I'm trying to add a new product id [1] to the driver udav and am
>> having a little trouble.
>>
>> At first, this is similar to id 0x8180 and there should be no
>> problems, but I still can not get a P
On 10 June 2011 14:17, Luiz Gustavo S. Costa wrote:
> I'm trying to add a new product id [1] to the driver udav and am
> having a little trouble.
>
> At first, this is similar to id 0x8180 and there should be no
> problems, but I still can not get a PHY for it.
Assuming you mean 0x8181 --looking
Hi list,
I'm trying to add a new product id [1] to the driver udav and am
having a little trouble.
At first, this is similar to id 0x8180 and there should be no
problems, but I still can not get a PHY for it.
Can someone help me?
System:
freekazoide# uname -a
FreeBSD freekazoide.luizgustavo.pro
