From: Dan Williams <dcbw@redhat.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Coelho Luciano (Nokia-D/Helsinki)" <Luciano.Coelho@nokia.com>
Subject: Re: wl12xx: driver for TI wl1251 chipset
Date: Tue, 10 Feb 2009 11:25:59 -0500 [thread overview]
Message-ID: <1234283159.3119.62.camel@localhost> (raw)
In-Reply-To: <87mycuxnum.fsf@nokia.com>
On Tue, 2009-02-10 at 18:23 +0200, Kalle Valo wrote:
> Dan Williams <dcbw@redhat.com> writes:
>
> >> production line tests and pushing the calibration data from user
> >> space.
> >
> > When is the calibration data required
>
> When we boot the firmware, that is during interface up.
>
> > and is it likely to change at runtime?
>
> It's device specific. Each device is calibrated in the factory and the
> calibration data is stored to a special partition in the device.
By "special partition", you mean a filesystem? Or something else?
> > What I really mean is, if the calibration data isn't required to
> > change while the interface is up, maybe use request_firmware() and
> > load it at device open time or something?
>
> request_firmware() has access only to the rootfs which the user can
> flash anytime he wants. So we would have to create the calibration
> file during every boot, or something like that. I guess it's doable
> but a bit ugly.
Yeah, that's somewhat ugly then.
Dan
next prev parent reply other threads:[~2009-02-10 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 10:32 wl12xx: driver for TI wl1251 chipset Kalle Valo
2009-02-10 15:21 ` Dan Williams
2009-02-10 16:23 ` Kalle Valo
2009-02-10 16:25 ` Dan Williams [this message]
2009-02-10 17:18 ` Kalle Valo
2009-02-19 9:19 ` Kalle Valo
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=1234283159.3119.62.camel@localhost \
--to=dcbw@redhat.com \
--cc=Luciano.Coelho@nokia.com \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
/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.