1 |
thegeezer <thegeezer@×××××××××.net> [14-10-06 20:48]: |
2 |
> On 06/10/14 17:34, meino.cramer@×××.de wrote: |
3 |
> > Hinnerk van Bruinehsen <h.v.bruinehsen@×××××××××.de> [14-10-06 17:56]: |
4 |
> >> On Sun, Oct 05, 2014 at 07:44:03PM +0200, meino.cramer@×××.de wrote: |
5 |
> >>> walt <w41ter@×××××.com> [14-10-05 19:36]: |
6 |
> >>>> On 10/05/2014 07:54 AM, meino.cramer@×××.de wrote: |
7 |
> >>>>> walt <w41ter@×××××.com> [14-10-05 16:16]: |
8 |
> >>>>>>> On 10/05/2014 06:52 AM, meino.cramer@×××.de wrote: |
9 |
> >>>>>>>>> Hi, |
10 |
> >>>>>>>>> |
11 |
> >>>>>>>>> while trying to get a mt7601sta (UWN200 WiFi dongle) driver running |
12 |
> >>>>>>>>> and working I came accross this in the dmesg output: |
13 |
> >>>>>>>>> |
14 |
> >>>>>>>>> [ 9.931938] usb 2-1: device v148f p7601 is not supported |
15 |
> >>>>>>> This looks to me like it's the real error, not the one below. |
16 |
> >>>>> What I dont understand is: If I provide the kernel driver...why does |
17 |
> >>>>> the kernel "decides" not to support the hardware the driver itsself |
18 |
> >>>>> supports...? |
19 |
> >>>> Where did you get the driver? Are you sure it's really the right one? |
20 |
> >>>> |
21 |
> >>>> |
22 |
> >>>> |
23 |
> >>> One of the main maintainer for the Beaglebone black kernel sources |
24 |
> >>> (Robert C. Nelson) point me to his git repository of this driver. |
25 |
> >>> |
26 |
> >>> I am now back to kernel 3.8.13, where this stuff runs... |
27 |
> >>> (The kernel I tried it before was 3.14.19) |
28 |
> >>> But this kernel version get no much updates thess days and is |
29 |
> >>> somehow old... |
30 |
> >>> |
31 |
> >> So you tried to run a driver for 3.8.x on a 3.14.x kernel? |
32 |
> >> Such things often result in breakage as, while the kernels interface to |
33 |
> >> userspace is very stable, the internal interfaces aren't stable at all. Likely |
34 |
> >> there would be some other stuff necessary to get the driver to work properly. |
35 |
> >> Some googling around led me to [1] though, which seems to imply that there is |
36 |
> >> support on newer kernels (3.15.10 and newer), if you use the right patch... |
37 |
> >> |
38 |
> >> So maybe you are sucessful with that... |
39 |
> >> |
40 |
> >> WKR |
41 |
> >> Hinnerk |
42 |
> >> |
43 |
> >> [1] http://www.spinics.net/lists/linux-wireless/msg126291.html |
44 |
> > |
45 |
> > Moin Hinnerk, |
46 |
> > (hopefully have guessed this greet correctly...I am from that |
47 |
> > part of Germany ;) |
48 |
> > |
49 |
> > I have the source of the driver exclusivly compiled for 3.8.13 |
50 |
> > as for 3.14.something (cant remember). |
51 |
> > 3.14.x has some other problems (on that embedded platform) like |
52 |
> > not powering off when shutdown, random reboots and such. |
53 |
> > So decided to go back to 3.8.13. |
54 |
> > Yesterday I started updateing (eix-sync and emerge) that Gentoo |
55 |
> > and it ends up in an endless loop (bash update) of configureing |
56 |
> > (damn slow on that mini iron) and compiling - |
57 |
> |
58 |
> just a small aside - you might like to read up on cross compiling and |
59 |
> save yourself a world of pain |
60 |
> http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml |
61 |
|
62 |
Thank you for the hint! |
63 |
I heard that before... ;) |
64 |
|
65 |
yeah...I walk through all this pain (cross compiling, distcc,...) |
66 |
allready. ;) |
67 |
|
68 |
Beside the kernel, which I compile on my PC and which |
69 |
got an excellent own cross compilling setup made by Robert Nelson, |
70 |
I compile all stuff natively on the embedded system itsself. |
71 |
Reason: |
72 |
The kernel does not depend on other things (especially header files, |
73 |
libs) except the cross compiler itsself and therefore is safe to be |
74 |
cross compiled. |
75 |
For everything else: I repeatedly struggled over software, which |
76 |
includes suddenly header files and libs from my PCs environment |
77 |
instead of the cross compiling sandbox for various reasons. |
78 |
Mostly hardcoded paths and such are the reason. |
79 |
Sometimes it works even with the PCs headers, sometimes it fails when |
80 |
executed, often it suddenly stops compiling. My PC is 64 bit, my |
81 |
embedded system is 32 bit. |
82 |
|
83 |
|
84 |
|
85 |
> > as it looks - |
86 |
> > of a single file. |
87 |
> > After more than 10 hours I CTRL-C that, reupated and now I am |
88 |
> > ...updateing the bash again. |
89 |
> > Sigh. |
90 |
> > Currently "fun" is something else... |
91 |
> > |
92 |
> > Is the 3.15.10++ branch free of things like random reboot and |
93 |
> > not powering off? |
94 |
> > |
95 |
> > Best regards, |
96 |
> > mcc |
97 |
> > |
98 |
> > |
99 |
> > |
100 |
> |
101 |
> |