| 1 |
Yeah, seem udev is the problem. |
| 2 |
|
| 3 |
I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/ |
| 4 |
|
| 5 |
It seems once this is done right, thing will work |
| 6 |
|
| 7 |
Thanks! |
| 8 |
|
| 9 |
(right now, it sees it as generic usb something...) |
| 10 |
|
| 11 |
Érico V. Porto |
| 12 |
|
| 13 |
|
| 14 |
On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@×××××.com> wrote: |
| 15 |
|
| 16 |
> Érico Porto wrote: |
| 17 |
> |
| 18 |
>> so now the module is loadable through modprobe, it all makes with no |
| 19 |
>> errors. |
| 20 |
>> |
| 21 |
>> It's probably out of this topic, but shouldn't I see a ttyUSB or |
| 22 |
>> something like that in my /dev/ ? |
| 23 |
>> |
| 24 |
>> I tried using |
| 25 |
>> |
| 26 |
>> modprobe ti_usb_3410_5052 product=0451 vendor f432 |
| 27 |
>> |
| 28 |
>> I just wanted to read the virtual usb serial out of a Texas launchpad |
| 29 |
>> board. This board uses the TUSB3410 chip. I'm asking about this in the |
| 30 |
>> texas forums too, just was surprised to see so many fast answers. |
| 31 |
>> |
| 32 |
>> Érico V. Porto |
| 33 |
>> |
| 34 |
>> |
| 35 |
> I would think udev would create the device when it is connected or you |
| 36 |
> boot up, whichever comes first. I have no knowledge on the device you are |
| 37 |
> using but do on the kernel part. If you load the module, udev should then |
| 38 |
> see the device and create the file in /dev. That's the theory anyway. You |
| 39 |
> can use udevadm monitor to see if udev sees it as it should. You can also |
| 40 |
> tail -f /var/log/messages to see what happens when you connect it or look |
| 41 |
> in dmesg. One or more of those should tell you what is not working. |
| 42 |
> |
| 43 |
> Dale |
| 44 |
> |
| 45 |
> :-) :-) |
| 46 |
> |
| 47 |
> |
Archives