On 14 November 2010 21:29, Andrew ni...@seti.kr.ua wrote:
14.11.2010 23:15, davidMbrooke пишет:
On Sat, 2010-11-13 at 20:50 +0200, Andrew wrote:
13.11.2010 12:24, davidMbrooke пишет:
On Sat, 2010-11-13 at 11:11 +0200, Andrew wrote:
12.11.2010 20:24, davidMbrooke пишет:
I see that we are
15.11.2010 14:25, e-mail dmb.leaf-devel пишет:
On 14 November 2010 21:29, Andrewni...@seti.kr.ua wrote:
14.11.2010 23:15, davidMbrooke пишет:
On Sat, 2010-11-13 at 20:50 +0200, Andrew wrote:
13.11.2010 12:24, davidMbrooke пишет:
On Sat, 2010-11-13 at 11:11 +0200, Andrew wrote:
12.11.2010
Am Montag, 15. November 2010, 14:09:29 schrieb Eric Spakman:
David,
If I remember correctly, the option Check tainted module is needed. But I
can't remember which modules needed it. Please check before commiting that
change.
Hi Eric
I guess you mean this one:
-enabled insmod tainted
Hi Kp,
That's it ;)
Eric
2010/11/15 KP Kirchdoerfer kap...@users.sourceforge.net
Am Montag, 15. November 2010, 14:09:29 schrieb Eric Spakman:
David,
If I remember correctly, the option Check tainted module is needed. But
I
can't remember which modules needed it. Please check before
Good catch guys; great teamwork! :-)
So I will leave things as per my previous diff, except I will disable
PRETTY_2.6_OUTPUT.
I will re-build BusyBox now, test and then commit to CVS.
dMb
On Mon, 2010-11-15 at 15:11 +0100, Eric Spakman wrote:
Hi Kp,
That's it ;)
Eric
2010/11/15
Hi,
I just uploaded a modified Bering-2.6.35.8.config (for
CONFIG_ATA_OVER_ETH) and in the process broke the kernel build.
The problem is that the i686 / i486 / geode patch files include the
timestamp on line 4. If this changes in the base
Bering-2.6.35.8.config the patches don't apply cleanly
