From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Google doesn't help Buildroot newcomers really much
Date: Sat, 9 Mar 2013 15:18:45 +0100 [thread overview]
Message-ID: <20130309151845.6a7da709@skate> (raw)
In-Reply-To: <CAMFO433vmKwUuc6ap2654izNBpchHu7_6wzG10MisbGO9rvF6w@mail.gmail.com>
Dear Marc Schultz,
On Sat, 9 Mar 2013 12:37:12 +0100, Marc Schultz wrote:
> I'd like to make buildroot running on a similar board of BF537-STAMP. Now I
> want to change the sound device to a Cirrus Logic CS4270, but after booting
> the uImage and loading as much sound modules as I can (e.g. snd-soc-cs4270)
> "aslactl init" says that there is no sound card. Do I have to modify the
> board file "linux/linux-kernel/arch/<my_arch>/mach-<board_arch>/<board>.c"
Unfortunately, this location is completely specific to the Analog
Devices fork of Buildroot. They have forked Buildroot some time ago,
and made a number of changes that move away from the standard
Buildroot. Which means that the official Buildroot documentation may or
may not apply to Analog Devices Buildroot fork, depending on which
specific topic you look at.
We have been discussing this problematic fork with Analog Devices
people just a few days ago, and apparently, they plan to rebase their
work on Buildroot 2013.02 and then start upstreaming their changes. But
that will probably take a long time, because they made many
modifications, some of them really moving away from what we want to
have in the standard Buildroot.
> and if yes, is there a good workflow for that to prevent
> hard-to-debug-mistakes?
>
> The ALSA-Project
> website<http://www.alsa-project.org/main/index.php/Matrix%3aModule-cs4270>
> shows
> a specific module named "snd-cs4270". Can I get this module installed by
> buildroot or do I have to download and integrate it into my target hardware
> on my own?
Your question is really a kernel development question rather than a
Buildroot question. Once you know how to make a simple modification to
your kernel sources, rebuild your kernel, and run it on your board,
then you should turn towards the ALSA SoC community to know in details
how to configure this sound codec for your board.
> I'm using the buildroot revision from
> Blackfin<http://docs.blackfin.uclinux.org/doku.php?id=buildroot:build-system:build_a_target>
> (2012.08)
> and I get this thing booting on my target hardware. Now I wanted to try the
> newest Buildroot revision (2013.05) from your website, but I always get a
> "No rule to make target `uImage'. Stop." compiling error. Any idea what I
> might have done wrong?
Can you show us your Buildroot .config (the one used with the mainline
Buildroot) ?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-09 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMFO431gatpdNG5oEcAQqCWVLs6St6-0P1SBA3h3SiTimk5tvg@mail.gmail.com>
2013-03-09 11:37 ` [Buildroot] Fwd: Google doesn't help Buildroot newcomers really much Marc Schultz
2013-03-09 14:18 ` Thomas Petazzoni [this message]
2013-03-11 14:23 ` Marc Schultz
2013-03-12 17:23 ` Arnout Vandecappelle
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=20130309151845.6a7da709@skate \
--to=thomas.petazzoni@free-electrons.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