All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Sander <msander@ripnet.com>
To: buildroot@busybox.net
Subject: [Buildroot] AT91SAM9G20 support?
Date: Thu, 30 Oct 2008 22:01:15 -0500	[thread overview]
Message-ID: <490A74FB.7020705@ripnet.com> (raw)
In-Reply-To: <103020081936.29280.490A0CB70005979E0000726022007504380401010C0A00009A9C@comcast.net>

suffecool at comcast.net wrote:
> Yeah, that's what I am discovering.  I am now looking at various kernel releases to see if and when 9G20 support was added (if at all).
>
> Google searching found this link:
> http://lkml.org/lkml/2008/6/13/62
>
> where it appears that somebody back in June 2008 did a lot of work patching the kernel to get the 9G20 to be supported.  I'm downloading the 2.6.27 kernel now to see if it was added  into that one.
>
> --kev
>
>   

Kevin,
 
You will need the 2.6.27 kernel.  I got a g20 on Friday and successfully 
booted it.  I used an oct 22 buildroot snapshot, and selected the 2.6.27 
kernel. I initially did the buildroot configuration for the 9260.    
After everything was completed I went back and did a kernel "make 
at91sam9g20ek_defconfig, and redid the top level "make".  From what I 
can see, there is no g20 support outside of the kernel (as of a few 
weeks ago).  

For my initial testing I grabbed pre build bootstrap & u-boot for the 
9g20 from linux4sam
(ftp://www.linux4sam.org/pub/uboot/u-boot-1.1.5_atmel_1.7/u-boot-1.1.5_atmel_1.7-at91sam9g20ek-dataflash.bin).      

(ftp://www.linux4sam.org/pub/at91bootstrap/AT91Bootstrap_9g20/dataflash_at91sam9g20ek.bin)

I suspect the buildroot bootstrap & u-boot will work fine, but I have 
not tested them.

HTH

Mike

  reply	other threads:[~2008-10-31  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 19:36 [Buildroot] AT91SAM9G20 support? suffecool at comcast.net
2008-10-31  3:01 ` Mike Sander [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30 18:51 suffecool at comcast.net
2008-10-30 19:27 ` hartleys

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=490A74FB.7020705@ripnet.com \
    --to=msander@ripnet.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 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.