Hi Gavin,
Gavin Lambert wrote:
Quoth Greg Ungerer:
Well in this sense there is no "libraries". You lost any notion of
them at the link stage. With no shared libraries all you have is
the final binaries. (Yes each will contain some of code that was in
the build library archives).
That's my poi
Gavin Lambert wrote:
> However this is also mitigated a bit if you can get XIP to work.
Fwiw, you can also do XIP in RAM, to reduce the footprint with
multiple instances of the same executable. I do this and it's a great
saving with several Busybox instances.
-- Jamie
___
Quoth Greg Ungerer:
> Well in this sense there is no "libraries". You lost any notion of
> them at the link stage. With no shared libraries all you have is
> the final binaries. (Yes each will contain some of code that was in
> the build library archives).
That's my point though. If linking to th
Hi Gavin,
Gavin Lambert wrote:
Quoth Greg Ungerer:
With any non-MMU environment big binaries are more problematic.
You need to find large contiguous regions to bring them in (assuming
you cannot run them XIP from within the filesystem they are in).
Small is better.
It's a little more murky th
Quoth Greg Ungerer:
> With any non-MMU environment big binaries are more problematic.
> You need to find large contiguous regions to bring them in (assuming
> you cannot run them XIP from within the filesystem they are in).
> Small is better.
It's a little more murky than that -- if don't have a l
For NPTL implementation, here is a paper about the implementation on the
uClibc http://www.kernel.org/doc/ols/2006/ols2006v1-pages-409-420.pdf.
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
Hi Michael,
Michael Schnell wrote:
I just have my first running uCLinux system in front of me (not created
by myself, but using a Kernel image and roof file system I got with the
hardware.
Of course I see that multiple programs are included in busybox.
This seems to be true for the command l
On Monday 31 March 2008, John Williams wrote:
>- child does execve("/bin/ls",NULL)
this is wrong. if it works anywhere, you're simply lucky.
-mike
signature.asc
Description: This is a digitally signed message part.
___
uClinux-dev mailing list
uCl
On Tuesday 01 April 2008, Xin Xie wrote:
> I did a test on the Coldfire V3 uClinux. I changed the
> "execve("/bin/ls",NULL)" to "execve("/bin/ps",NULL)", because of some
> problem to exec the busybox linked "ls". However, I did get exactly same
> behavior as you described.
you're calling execve()
> Basically we have parent that
>
> 1. blocks all signals
> 2. spawns a thread (SigHandler)
> 3. vforks()
>- child does execve("/bin/ls",NULL)
>- parent sleep() loops forever
>
> The SigHandler thread
>
> 1. blocks all signals
> 2. does a sigwait() loop
> if SIGCHLD delivered,
>
Jivin Greg Ungerer lays it down ...
> Hi Bob, Phil,
>
> Phil Wilshire wrote:
> >Hi Bob,
> >Use eraseall to erase the entire partition
> >
> >eraseall /dev/mtdx
> >
> >Then use cp to write to the flash.
> >
> >cp /var/myimage /dev/mtdx
> >
> >Where x is the kernel image partition.
>
> You need to
Hi Bob, Phil,
Phil Wilshire wrote:
Hi Bob,
Use eraseall to erase the entire partition
eraseall /dev/mtdx
Then use cp to write to the flash.
cp /var/myimage /dev/mtdx
Where x is the kernel image partition.
You need to be careful if the "eraseall /dev/mtdx"
is erasing the contents of your ro
Hi,
I did a test on the Coldfire V3 uClinux. I changed the
"execve("/bin/ls",NULL)" to "execve("/bin/ps",NULL)", because of some
problem to exec the busybox linked "ls". However, I did get exactly same
behavior as you described.
My first suspection is using the LinuxThread in the uClibc means a
Hi Phil .. again!
Sorry, perhaps I should have tried this first, before my last email.
Anyway, I tried simply adding this line:
mtdblock0,b,31,0 mtd0,c,90,0 \
in my Makefile, and sure enough, I now have /dev/mtd0 and
/dev/mtdblock0. Furthermore, the commands you mentioned appear to
work, at
Hi Phil,
On Tue, Apr 1, 2008 at 1:56 PM, Phil Wilshire <[EMAIL PROTECTED]> wrote:
> Hi Bob .. again
>
> If you see partitions in
> cat /proc/mtd
> or
> cat /proc/partitions
>
> then you can mainly ignore the last email.
Okay, this is what my system gives me:
/> cat /proc/mtd
dev:
Hi Bob .. again
If you see partitions in
cat /proc/mtd
or
cat /proc/partitions
then you can mainly ignore the last email.
The actual entries in /dev are normally made in the
vendors///Makefile.
Some architectures like the Blackfin have a
device_table.txt
file to specify the /dev entries.
Som
Hi Bob,
You need to look at some of the drivers/mtd/maps/*.c files
to get some ideas.
One interesting option is command line partitioning.
Once again look through the drivers/mtd directory for clues.
look at drivers/mtd/maps/uclinux.c for example.
remember each partition must start and end on
On Tue, Apr 1, 2008 at 9:42 AM, Phil Wilshire <[EMAIL PROTECTED]> wrote:
> Hi Bob,
> Use eraseall to erase the entire partition
>
> eraseall /dev/mtdx
>
> Then use cp to write to the flash.
>
> cp /var/myimage /dev/mtdx
Oh, that certainly sounds easy enough! But...
>
> Where x is the kernel
thank so much
Envoyé avec Yahoo! Mail.Plus de moyens pour rester en contact.
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To un
On Tuesday 01 April 2008, dinesh babu wrote:
> i have compilied uboot (u-boot-1.1.6-2008R1 taken from
> blackfin.uclinux.org)
you've posted this same question twice in the forums, and you're cross-posting
to multiple lists. please do not do this. you ask your question once, in
one place, rath
Hi Bob,
Use eraseall to erase the entire partition
eraseall /dev/mtdx
Then use cp to write to the flash.
cp /var/myimage /dev/mtdx
Where x is the kernel image partition.
Phil Wilshire
SDCS
Bob Grimes wrote:
My client wants the ability to upload a new image, and write it into
boot NOR fl
i have compilied uboot (u-boot-1.1.6-2008R1 taken from blackfin.uclinux.org)in
fedora 7 .i have used the latest tool chain release(
blackfin-toolchain-08r1-8.i386). but i have the following errors .can any
boby help me
errors generated when i compile u-boot
In file included from hello_world.c:2
My client wants the ability to upload a new image, and write it into
boot NOR flash. We have uBoot, but in many deployments, neither the
serial port nor Ethernet will be available, so we can't use uBoot to
do this. We have the basic idea of uploading (over USB Gadget serial)
a new image, storing
23 matches
Mail list logo
