From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Rafał Miłecki" <rafal@milecki.pl>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] board/broadcom: add support for bcm47xx platform devices
Date: Thu, 13 Jan 2022 22:42:52 +0100 [thread overview]
Message-ID: <20220113224252.0a46e30b@windsurf> (raw)
In-Reply-To: <20211021085540.18764-1-zajec5@gmail.com>
Hello Rafał,
On Thu, 21 Oct 2021 10:55:40 +0200
Rafał Miłecki <zajec5@gmail.com> wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Broadcom's bcm47xx is a family of MIPS SoCs going back to the 2002 and
> including e.g. Linksys WRT54G with its BCM4702. It evolved through years
> and its latest model BCM4706 is still in use nowadays.
>
> Pretty much all SoCs contain all following components:
> 1. CPU
> 2. PCIe controller(s)
> 3. Ethernet interface(s)
> 4. USB controllers
> 5. Serial flash controller
> 6. GPIO controller (for LEDs and buttons)
> 7. Watchdog
>
> Upstream kernel includes a pretty much complete support for bcm47xx but
> it isn't DTS based. Board detection is handled on runtime so there is
> one kernel image to serve all.
>
> Bootloader used in those devices is CFE. It allows booting kernel over
> tftp and flashing firmwares using TRX format. It isn't properly open
> sourced (except some early versions) and in practice it's irreplaceable.
>
> This commit adds support for building a bootable kernel based on 5.4
> stable release:
> Starting program at 0x80001000
> Linux version 5.4.155 (rmilecki@localhost.localdomain) (gcc version 10.3.0 (Buildroot 2021.08-930-gc0c925605d)) #5 Thu Oct 21 10:16:20 CEST 2021
>
> Linux 5.10 doesn't start booting due to some regression that remains to
> be debugged. Adding support for building full images (including rootfs)
> is also planned for the future.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> board/broadcom/bcm47xx/linux.config | 28 ++++++++++++++++++++++++++++
> configs/broadcom_bcm47xx_defconfig | 8 ++++++++
> 2 files changed, 36 insertions(+)
> create mode 100644 board/broadcom/bcm47xx/linux.config
> create mode 100644 configs/broadcom_bcm47xx_defconfig
Thanks for this contribution, but it doesn't seem to be really useful
as it is: the root filesystem generated as a tarball is not even used,
and there is no readme.txt. We prefer to have directly useful defconfig
files.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-13 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 8:55 [Buildroot] [PATCH] board/broadcom: add support for bcm47xx platform devices Rafał Miłecki
2022-01-13 21:42 ` Thomas Petazzoni [this message]
2022-01-13 21:56 ` Rafał Miłecki
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=20220113224252.0a46e30b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=rafal@milecki.pl \
--cc=zajec5@gmail.com \
/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.