Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Cirrus  EP93XX  ARM to buildroot
Date: Wed, 03 Oct 2007 02:42:24 +0300	[thread overview]
Message-ID: <4702D760.4020707@promwad.com> (raw)
In-Reply-To: <1191361900.4187.48.camel@localhost.localdomain>

Brian Austin ?????:
> All,
> 
> I would like to start the process of adding the Cirrus Logic EP93XX ARM9
> family to buildroot.
> 
> couple things about the 93xx.
> 
> 1.  Maverick Crunch  FPU.  I have patches for GCC/uClibc to enable
> Crunch FPU.
> 
> 2. Linux Kernel.  We have a patch for several current kernel versions up
> to 2.6.21.5.
> 
> I also have patches for DirectFB which I submitted last week and QT,
> TSLIB, and other BSP software which have not been submitted.
> 
> I also think there is a section for bootloaders as well?
> 
> Qustion is,  where to start?
> 
> Right now we give out a modified version of buildroot for the prebuilt
> toolchain and a buildroot system for building the kernel, u-boot,
> redboot (ecos), and BSP software.  But I want it to go into ya'lls to
> make things more consistent.  it's hard for me to do everything here.
> We use DirectFB/GTK now for our graphics and I had to change alot to get
> it to build and install correctly to pass SQA testing, so hopefully that
> can be of use as well.
> 
> anyway comments and suggestions on where to start would be great.
> 
> Regards,
> Brian Austin
> Cirrus Logic Inc. 
> 
> 

Hi Brian,

That's great that Cirrus decided to merge its verion of buildroot with mainline.
I was thinking to start adding Cirrus stuff to buildroot by myself, because we use EP93xx
 but need packages present in mainline buildroot.

Now that's a good chance to join efforts so that Cirrus EP93xx integration into buildroot go quickly.

I'd suggest you to take a look into target/device dir
and create layout for target/device/Cirrus

And start posting your patches. I think patches for packages are not very Cirrus CPU specific.

Best regards,
Ivan

--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

  reply	other threads:[~2007-10-02 23:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 21:51 [Buildroot] Adding Cirrus EP93XX ARM to buildroot Brian Austin
2007-10-02 23:42 ` Ivan Kuten [this message]
2007-10-03 20:40   ` Bernhard Fischer
2007-10-03 22:54     ` Ivan Kuten
2007-10-04  4:08       ` Ulf Samuelsson
2007-10-04 13:46         ` Brian Austin
2007-10-06 20:15         ` Bernhard Fischer
2007-10-07 17:45           ` Ivan Kuten
2007-10-07 17:00             ` Bernhard Fischer

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=4702D760.4020707@promwad.com \
    --to=ivan.kuten@promwad.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox