1 |
2011/11/7 Érico Porto <ericoporto2008@×××××.com>: |
2 |
> oh no, I don't think it is a bug. |
3 |
> I mean, this is suposed to be open using some tool named mspdebug of some |
4 |
> sorta: http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/ |
5 |
> But I know this chip is a usb to serial adapter, only the product Id is |
6 |
> exchanged to be a Development Tool. To change the vendor and product id, I |
7 |
> found a how-to here |
8 |
> : http://www.brimson.com/downloads/ti_usb_multitech_release_notes-1.1.txt |
9 |
> It doesn't seem to do nothing, but maybe I have to write some code on the |
10 |
> msp before. I haven't used this board much, but it is the only thing I have |
11 |
> to test now - I need to interface with a gps chip, but I have no serials |
12 |
> available, so later I plan to use this chip. I know I have loaded this as a |
13 |
> serial long before... |
14 |
> Érico V. Porto |
15 |
> |
16 |
> |
17 |
> On Sun, Nov 6, 2011 at 9:58 PM, Aljosha Papsch <papsch.al@××××××××××.com> |
18 |
> wrote: |
19 |
>> |
20 |
>> 2011/11/7 Érico Porto <ericoporto2008@×××××.com>: |
21 |
>> > Yeah, seem udev is the problem. |
22 |
>> > I'm reading http://hackaday.com/2009/09/18/how-to-write-udev-rules/ |
23 |
>> > It seems once this is done right, thing will work |
24 |
>> > Thanks! |
25 |
>> > (right now, it sees it as generic usb something...) |
26 |
>> > Érico V. Porto |
27 |
>> > |
28 |
>> > |
29 |
>> > On Sun, Nov 6, 2011 at 9:20 PM, Dale <rdalek1967@×××××.com> wrote: |
30 |
>> >> |
31 |
>> >> Érico Porto wrote: |
32 |
>> >>> |
33 |
>> >>> so now the module is loadable through modprobe, it all makes with no |
34 |
>> >>> errors. |
35 |
>> >>> |
36 |
>> >>> It's probably out of this topic, but shouldn't I see a ttyUSB or |
37 |
>> >>> something like that in my /dev/ ? |
38 |
>> >>> |
39 |
>> >>> I tried using |
40 |
>> >>> |
41 |
>> >>> modprobe ti_usb_3410_5052 product=0451 vendor f432 |
42 |
>> >>> |
43 |
>> >>> I just wanted to read the virtual usb serial out of a Texas launchpad |
44 |
>> >>> board. This board uses the TUSB3410 chip. I'm asking about this in the |
45 |
>> >>> texas |
46 |
>> >>> forums too, just was surprised to see so many fast answers. |
47 |
>> >>> |
48 |
>> >>> Érico V. Porto |
49 |
>> >>> |
50 |
>> >> |
51 |
>> >> I would think udev would create the device when it is connected or you |
52 |
>> >> boot up, whichever comes first. I have no knowledge on the device you |
53 |
>> >> are |
54 |
>> >> using but do on the kernel part. If you load the module, udev should |
55 |
>> >> then |
56 |
>> >> see the device and create the file in /dev. That's the theory anyway. |
57 |
>> >> You |
58 |
>> >> can use udevadm monitor to see if udev sees it as it should. You can |
59 |
>> >> also |
60 |
>> >> tail -f /var/log/messages to see what happens when you connect it or |
61 |
>> >> look in |
62 |
>> >> dmesg. One or more of those should tell you what is not working. |
63 |
>> >> |
64 |
>> >> Dale |
65 |
>> >> |
66 |
>> >> :-) :-) |
67 |
>> >> |
68 |
>> > |
69 |
>> > |
70 |
>> |
71 |
>> I'm also not familiar with your device, but some devices need to be |
72 |
>> mode switched manually if they show up as something different. You can |
73 |
>> use usb-modeswitch for that or some more convenient tool like sakis3g: |
74 |
>> http://www.sakis3g.org/ |
75 |
>> |
76 |
>> Btw: I'll report a bug in Gentoo's Bugzilla regarding your (and mine) |
77 |
>> problem. Maybe others are affected too and this option can be switched |
78 |
>> off at least for genkernel users. |
79 |
>> |
80 |
> |
81 |
> |
82 |
|
83 |
Sorry, I wasn't clear enough: I reported the bug, that installation of |
84 |
the kernel will fail if FIRMWARE_IN_KERNEL is enabled. You can add you |
85 |
to the list, if you want: |
86 |
https://bugs.gentoo.org/show_bug.cgi?id=389775 |