You should probably try the RA73 website, or the wlan mailing list for
this question.
from my experience with the RA73 for EP93XX, I never needed firmware to
be loaded.
Did you enable firmware loading in the kernel?
-Original Message-
From: Manuel Sahm <[EMAIL PROTECTED]>
To: busybox@b
Are you by chance trying to build for a samsung arm?
-Original Message-
From: mys shekar <[EMAIL PROTECTED]>
To: busybox@busybox.net
Subject: kernel compilation ("__LINUX_ARM_ARCH__" is not defined)
Date: Wed, 27 Feb 2008 12:13:07 -0800
Hi ,
I am trying to compile linux kernel 2.6.24
Correct.
You are mixing EABI and non EABI. You should build (if your doin EABI)
your toolchain with 2.6.16 or greater headers.
The main reason, from my experiences a while back, with init in busybox
hanging and using EABI was that either the kernel was built with EABI
and busybox was not or the
did you make that toolchain yourself?
I would suggest using a 4.x with a 2.3.4 of higher c library
On Wed, 2007-09-12 at 12:09 -0400, Paul Barrette wrote:
> Update busybox or my toolchain? I don't plan on updating my
> toolchain, this one is sanitized and a lot depends on it. Besides, it
>
what version are you using?
the newer ones have 3 I believe. But I'm not exactly sure since we use
uClibc mostly
On Wed, 2007-09-12 at 10:21 -0400, Paul Barrette wrote:
> Glibc's sched_setaffinity only has two args
> extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)
>
>
eat.
>
>
> Regards,
> Vivek :-
> -Original Message-
> From: Brian Austin [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 21, 2007 8:38 PM
> To: Vivek-Kumar Gupta
> Cc: busybox@busybox.net
> Subject: Re: disable network module at boot time
>
> That m
That means your network subsystem drivers are loading. Not the physical
Ethernet Device.
For a device you should see something like this.
ep93xx-eth version 0.1 loading
eth0: ep93xx on-chip ethernet, IRQ 39, 00:0e:3a:11:22:33.
what you are seeing is networking support, not device support.
Lik
On Thu, 2007-05-10 at 22:20 +0200, Denis Vlasenko wrote:
> On Wednesday 09 May 2007 14:54, Brian Austin wrote:
> > > make a symlink /bin/sh -> /bin/busybox and boot with init=/bin/sh
> > > --
> > > vda
> > >
> >
> > I have /bin/sh pointe
On Wed, 2007-05-09 at 20:46 +0200, Denis Vlasenko wrote:
> On Wednesday 09 May 2007 14:15, Brian Austin wrote:
> > On Wed, 2007-05-09 at 11:03 -0700, Larry Brigman wrote:
> > > On 5/9/07, Brian Austin <[EMAIL PROTECTED]> wrote:
> > > > On Wed, 2007-05-09
On Wed, 2007-05-09 at 20:46 +0200, Denis Vlasenko wrote:
> On Wednesday 09 May 2007 14:15, Brian Austin wrote:
> > On Wed, 2007-05-09 at 11:03 -0700, Larry Brigman wrote:
> > > On 5/9/07, Brian Austin <[EMAIL PROTECTED]> wrote:
> > > > On Wed, 2007-05-09
On Wed, 2007-05-09 at 11:03 -0700, Larry Brigman wrote:
> On 5/9/07, Brian Austin <[EMAIL PROTECTED]> wrote:
> > On Wed, 2007-05-09 at 12:30 -0400, Mike Frysinger wrote:
> > > On Wednesday 09 May 2007, Brian Austin wrote:
> > > > anyone have issues with in
On Wed, 2007-05-09 at 12:30 -0400, Mike Frysinger wrote:
> On Wednesday 09 May 2007, Brian Austin wrote:
> > anyone have issues with init in EABI busybox?
>
> most likely an EABI issue rather than a busybox issue ... as such, you should
> ask on the arm mailing lists as they pr
Hello,
running busybox 1.2.0
uclibc 0.9.29
gcc-4.1.2 EABI toolchain.
when booting kernel 2.6.20.4
with init=/bin/busybox sh
I get this error
Freeing init memory: 132K
Failed to execute '/bin/busybox. Attempting defaults...
I have made my own static and shared init ( hello world ) and th
Hello,
I have a gcc-4.1.2 EABi toolchain with uClibc-0.9.29.
compile is fine, kernel boots, I can create my own init ( hello world ),
I can even run init=/bin/busybox.
but just using init itself, it hangs with...
Freeing init memory: 132K
I am using busybox-1.2.0, I have tried all of them up t
14 matches
Mail list logo
