From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] board: add support for Warpboard
Date: Fri, 26 Jun 2015 00:38:23 +0200 [thread overview]
Message-ID: <20150625223823.GI4178@free.fr> (raw)
In-Reply-To: <558C800F.5030702@mind.be>
Arnout, Arthur, All,
On 2015-06-26 00:26 +0200, Arnout Vandecappelle spake thusly:
> On 06/25/15 10:54, Arthur LAMBERT wrote:
> > Arnout, All,
> >
> > Le Wednesday 24 Jun 2015 ? 23:46:52 (+0200), Arnout Vandecappelle a ?crit :
> >>> +
> >>> +Enable bluetooth
> >>> +================
> >>> +hciattach /dev/ttymxc4 any
> >>> +hciconfig hci0 up
> >>> +
> >>> +Enable Wifi
> >>> +==========
> >>> +modprobe brcmfmac
> >>> +ifconfig wlan0 up
> >>
> >> To do something useful, you'll also need a wpa-supplicant I guess...
> >>
> >> Since you anyway have a rootfs overlay, you could add init scripts to start
> >> wifi and bluetooth. We don't usually do that, but I think it would be a good idea.
> >
> > In fact I need bluez-util (to be able to run hciattach command also). And yes I also need wpa_supplicant for wifi.
> > So ok I will enable these two packages and add init script
>
> Question for the other BR developers (especially Peter): do you agree it's a
> good idea to make a non-minimal defconfig that includes bluez and wpa_supplicant?
Our board defconfig files are ususally just enough to bring up the board
and get a shell in there. If network is wired, then a dhcp client is OK
(usually udhcpc from busybox).
Everything (bluez and wpa-supplicant included) else is out of scope for
a defconfig, IMHO.
One case where I'd be inclined to accept more than the above is a
full-wireless device (like the soon-to-come-I-hope 96boards stuff).
But since wpa-supplicant needs configuration that we can't provide
(SSID and key), I don't see the point of adding it to the defconfig.
However, we've decided to accept "demo" defconfigs, which can be packed
with more features than a simple board defconfig. We haven't had any
single such demo defconfig submitted so far.
Still, even if we accept demo defconfigs, I stil think we should have a
small board defconfig file before we get a demo.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-06-25 22:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:46 [Buildroot] [PATCH v2 1/1] board: add support for Warpboard Arthur LAMBERT
2015-06-22 17:13 ` Arthur Lambert
2015-06-24 9:32 ` Arthur LAMBERT
2015-06-24 21:46 ` Yann E. MORIN
2015-06-24 21:47 ` Arnout Vandecappelle
2015-06-24 21:46 ` Arnout Vandecappelle
2015-06-25 8:54 ` Arthur LAMBERT
2015-06-25 22:26 ` Arnout Vandecappelle
2015-06-25 22:38 ` Yann E. MORIN [this message]
2015-06-26 12:24 ` Arthur LAMBERT
2015-06-26 13:23 ` Ryan Barnett
2015-06-26 15:06 ` Yann E. MORIN
2015-06-26 21:54 ` Arnout Vandecappelle
2015-06-25 12:07 ` Arthur LAMBERT
2015-06-25 22:41 ` 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=20150625223823.GI4178@free.fr \
--to=yann.morin.1998@free.fr \
--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