All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
To: openembedded-devel@lists.openembedded.org
Subject: Re: building uClinux using OE
Date: Tue, 19 Feb 2008 14:07:07 +0100	[thread overview]
Message-ID: <20080219130707.GD27792@deadlock.dhs.org> (raw)
In-Reply-To: <37367b3a0802170728r226edd39r5e8fd7c2f4fa869b@mail.gmail.com>

Hi, 

On Sun, Feb 17, 2008 at 12:28:27PM -0300, Alan Carvalho de Assis wrote:
> > uClibc is also already supported by OE, not sure if I would have to add
> > an option for uC-libc.
> >
> Although uC-libc is not so "up to date" I think it can be important to
> device with small flash memory (like Netburn MOD5272) since it create
> smallest binary footprint.

I will probably start with uClibc since it's already in OE, I am not sure
if my project requires uC-libc, I guess I will look at that when I get a
little further.

> > I do not have any uClinux experience yet, and it seems to be quite difficult
> > to gather all the bits and pieces of information, so I'd appreciate comments
> > and suggestions, especially if you see that I am missing something.
> >
> > I'd also be interested in your thoughts on what would be the best way to
> > integrate it into OE.
> >
> 
> Do you add all kernels supported by uClinux distro (2.0.x, 2.4.x and 2.6.x) ?

I will focus on 2.6.x, I do not have any hardware to test with the 
older kernels and the project I am working on also requires a 2.6.x version.
 
> I think your idea to add uClinux support on OE is fantastic!

Let's hope we succeed in doing so :)

Kind regards,
Jin





      reply	other threads:[~2008-02-19 13:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 15:55 building uClinux using OE Sergey 'Jin' Bostandzhyan
2008-02-14 16:47 ` Koen Kooi
2008-02-19 13:01   ` Sergey 'Jin' Bostandzhyan
2008-02-22 18:32   ` Sergey 'Jin' Bostandzhyan
2008-02-17 15:28 ` Alan Carvalho de Assis
2008-02-19 13:07   ` Sergey 'Jin' Bostandzhyan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080219130707.GD27792@deadlock.dhs.org \
    --to=jin@mediatomb.cc \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.