All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: Anton Kornilevsky <kornilevsky@cato-gmbh.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Adding support to a variant of an already supported MCU
Date: Thu, 11 Nov 2021 18:08:48 +0100	[thread overview]
Message-ID: <20211111170847.jkvvxcjxvoreh7ac@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <c73dab514fed4b4caa7ed80739fcc029@WINHEXBEEU126.win.mail>


[-- Attachment #1.1: Type: text/plain, Size: 1545 bytes --]

Hei hei,

On Thu, Nov 11, 2021 at 02:39:00PM +0000, Anton Kornilevsky wrote:
> I have been tasked with rebuilding a linux kernal for a board that
> is using the AT91SAM9261 MCU.

Which is still supported by recent Linux Kernel AFAIK.

> The buildroot support for this MCU has been dropped sometimes back in 2015, 

Can you point to some actual commits?

> and I was unable to rebuild the kernal using the last supported
> version of buildroot, due to an error related to the integrity of
> the zipfile containing the sam-ba utility. I seems like the older
> sam-ba utility versions are no longer to be found on microchips
> servers.

I might have those lying around somewhere, but you don't need those
for running on the target anyways, do you?

> How would one go about adding support to a variant of an MCU that is
> already supported by Buildroot? Is this even possible?

I just looked briefly over the defconfigs in buildroot's 'configs'
folder and at91sam9g20dfc_defconfig and at91sam9260eknf_defconfig
should be from the same at91 family. That should be a good start to
come up with a toolchain at least?

For building a recent kernel, at91_dt_defconfig in kernel tree should
give you a starting point?

Good luck!
Alex

-- 
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN     | speech censured, the first thought forbidden, the
 X  AGAINST      | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL    | (Jean-Luc Picard, quoting Judge Aaron Satie)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-11-11 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 14:39 [Buildroot] Adding support to a variant of an already supported MCU Anton Kornilevsky
2021-11-11 17:08 ` Alexander Dahl [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=20211111170847.jkvvxcjxvoreh7ac@falbala.internal.home.lespocky.de \
    --to=post@lespocky.de \
    --cc=buildroot@buildroot.org \
    --cc=kornilevsky@cato-gmbh.de \
    /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.