From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Robert Nelson <robertcnelson@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [PATCH v2] omap: beagle: add support for wl1271 on the board file
Date: Thu, 23 Sep 2010 15:52:33 +0300 [thread overview]
Message-ID: <1285246353.3231.84.camel@chilepepper> (raw)
In-Reply-To: <AANLkTimce-=MP2DDNTpRh_oRFW15_gSkKZJ6fQzwc4yJ@mail.gmail.com>
On Thu, 2010-09-23 at 14:03 +0200, ext Robert Nelson wrote:
> On Thu, Sep 23, 2010 at 5:30 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> > On Thu, Sep 23, 2010 at 11:20 AM, Luciano Coelho
> > <luciano.coelho@nokia.com> wrote:
> >> Add board configuration for the wl1271 daughter board. This patch is based
> >> on Ohad Ben-Cohen's patches for Zoom boards.
> >
> > Hm can that daughter board be detected? With your patch all beagle
> > users will get GPIO139 toggled, and if someone has that wired to
> > chainsaw switch somebody might get hurt.
>
> Expansion boards really need to follow:
>
> http://elinux.org/BeagleBoardPinMux#Expansion_boards
>
> Is there any eeprom on i2c bus #2 for identification on this board?
Hmmm... <checking the schematics>
Yes, it does. :) This makes perfect sense.
My bootloader (U-Boot 2010.03) doesn't seem to detect it, though:
<clip>
Probing for expansion boards, if none are connected you'll see a
harmless I2C error.
No EEPROM on expansion board
<clip>
Do I need a special bootloader?
Is there any standard way to recognize the expansion board and configure
it properly?
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-09-23 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 8:20 [PATCH v2] omap: beagle: add support for wl1271 on the board file Luciano Coelho
2010-09-23 10:30 ` Grazvydas Ignotas
2010-09-23 11:56 ` Luciano Coelho
2010-09-23 12:03 ` Robert Nelson
2010-09-23 12:52 ` Luciano Coelho [this message]
2010-09-23 13:42 ` Robert Nelson
2010-09-23 18:52 ` Luciano Coelho
2010-09-23 11:45 ` Felipe Balbi
2010-09-23 12:17 ` Luciano Coelho
2010-09-23 12:20 ` Felipe Balbi
2010-09-23 12:28 ` Luciano Coelho
2010-09-23 12:29 ` Felipe Balbi
2010-09-23 12:46 ` Ohad Ben-Cohen
2010-09-23 12:50 ` Felipe Balbi
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=1285246353.3231.84.camel@chilepepper \
--to=luciano.coelho@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=robertcnelson@gmail.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).