On 12.12.2013 21:55, Ben Hutchings wrote:
On Wed, 2013-12-11 at 16:53 -0600, Dan Williams wrote:
On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea.
On Wed, 2013-12-11 at 16:53 -0600, Dan Williams wrote:
> On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
> > On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
> > > On 11.12.2013 23:17, Ben Hutchings wrote:
> > > > I think that's an even worse idea. This is not firmware and it
Hello.
On 12-12-2013 2:36, Ivajlo Dimitrov wrote:
2. NVRAM reading is done by a tiny driver that is loaded based on the
platform name and updates the DT node in memory. (But I don't know how
wl1251 should decide to defer probing if it's probed before that other
driver.)
Ben.
Maybe a
On Wed 2013-12-11 21:17:34, Ben Hutchings wrote:
> On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
> > On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
> > > On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> > > > On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> > > > >
On Wed 2013-12-11 21:17:34, Ben Hutchings wrote:
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10
Hello.
On 12-12-2013 2:36, Ivajlo Dimitrov wrote:
2. NVRAM reading is done by a tiny driver that is loaded based on the
platform name and updates the DT node in memory. (But I don't know how
wl1251 should decide to defer probing if it's probed before that other
driver.)
Ben.
Maybe a
On Wed, 2013-12-11 at 16:53 -0600, Dan Williams wrote:
On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea. This is not firmware and it already
On 12.12.2013 21:55, Ben Hutchings wrote:
On Wed, 2013-12-11 at 16:53 -0600, Dan Williams wrote:
On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea.
On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
> On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
> > On 11.12.2013 23:17, Ben Hutchings wrote:
> > > I think that's an even worse idea. This is not firmware and it already
> > > exists in separate storage.
> > >
> > > I think that
On 12.12.2013 00:15, Ben Hutchings wrote:
2. NVRAM reading is done by a tiny driver that is loaded based on the
platform name and updates the DT node in memory. (But I don't know how
wl1251 should decide to defer probing if it's probed before that other
driver.)
Ben.
Maybe a "hwmac"
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
> On 11.12.2013 23:17, Ben Hutchings wrote:
> > I think that's an even worse idea. This is not firmware and it already
> > exists in separate storage.
> >
> > I think that rx51_init_wl1251() in
> >
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea. This is not firmware and it already
exists in separate storage.
I think that rx51_init_wl1251() in
arch/arm/mach-omap2/board-rx51-peripherals.c should either copy the MAC
address out of NVRAM, or if it's too early to
On Wed, 2013-12-11 at 21:17 +, Ben Hutchings wrote:
> On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
[...]
> > Maybe another way could be to use request_firmware to load address
> > from userspace... Or what do you think?
>
> I think that's an even worse idea. This is not firmware and
On Tue, 2013-12-10 at 20:31 +0100, Pali Rohár wrote:
[...]
> So, if you like this idea, can you help me how to write udev rule
> which will run my own program (it print mac address) and send mac
> address when driver ask for mac address in request_firmware?
> Problem is that default udev rule
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
> On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
> > On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> > > On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> > > > On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> > >
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár
On Tue, 2013-12-10 at 20:31 +0100, Pali Rohár wrote:
[...]
So, if you like this idea, can you help me how to write udev rule
which will run my own program (it print mac address) and send mac
address when driver ask for mac address in request_firmware?
Problem is that default udev rule for
On Wed, 2013-12-11 at 21:17 +, Ben Hutchings wrote:
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
[...]
Maybe another way could be to use request_firmware to load address
from userspace... Or what do you think?
I think that's an even worse idea. This is not firmware and it
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea. This is not firmware and it already
exists in separate storage.
I think that rx51_init_wl1251() in
arch/arm/mach-omap2/board-rx51-peripherals.c should either copy the MAC
address out of NVRAM, or if it's too early to
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea. This is not firmware and it already
exists in separate storage.
I think that rx51_init_wl1251() in
arch/arm/mach-omap2/board-rx51-peripherals.c should
On 12.12.2013 00:15, Ben Hutchings wrote:
2. NVRAM reading is done by a tiny driver that is loaded based on the
platform name and updates the DT node in memory. (But I don't know how
wl1251 should decide to defer probing if it's probed before that other
driver.)
Ben.
Maybe a hwmac property
On Wed, 2013-12-11 at 22:15 +, Ben Hutchings wrote:
On Wed, 2013-12-11 at 23:35 +0200, Ivajlo Dimitrov wrote:
On 11.12.2013 23:17, Ben Hutchings wrote:
I think that's an even worse idea. This is not firmware and it already
exists in separate storage.
I think that
On Tuesday 10 December 2013 20:22:19 Dan Williams wrote:
> On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
> > On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
> > > On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> > > > On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> >
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
> On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
> > On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> > > On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> > > > On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> > >
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
> On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> > On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> > > On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> > > > Pali Rohár writes:
> > > > > Driver wl1251 generating mac
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
> On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> > On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> > > Pali Rohár writes:
> > > > Driver wl1251 generating mac address randomly at startup
> > > > and there is no way to set
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
> On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> > Pali Rohár writes:
> > > Driver wl1251 generating mac address randomly at startup
> > > and there is no way to set permanent mac address via
> > > SET_IEEE80211_PERM_ADDR. This
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
> Pali Rohár writes:
> > Driver wl1251 generating mac address randomly at startup and
> > there is no way to set permanent mac address via
> > SET_IEEE80211_PERM_ADDR. This patch export sysfs file which
> > can set permanent mac address by
Pali Rohár writes:
> Driver wl1251 generating mac address randomly at startup and there is no way
> to
> set permanent mac address via SET_IEEE80211_PERM_ADDR. This patch export sysfs
> file which can set permanent mac address by userspace helper program. Patch is
> needed for devices which do
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár
On Tuesday 10 December 2013 20:22:19 Dan Williams wrote:
On Tue, 2013-12-10 at 18:52 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On
Pali Rohár pali.ro...@gmail.com writes:
Driver wl1251 generating mac address randomly at startup and there is no way
to
set permanent mac address via SET_IEEE80211_PERM_ADDR. This patch export sysfs
file which can set permanent mac address by userspace helper program. Patch is
needed for
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár pali.ro...@gmail.com writes:
Driver wl1251 generating mac address randomly at startup and
there is no way to set permanent mac address via
SET_IEEE80211_PERM_ADDR. This patch export sysfs file which
can set permanent mac
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár pali.ro...@gmail.com writes:
Driver wl1251 generating mac address randomly at startup
and there is no way to set permanent mac address via
SET_IEEE80211_PERM_ADDR.
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár pali.ro...@gmail.com writes:
Driver wl1251 generating mac address randomly at startup
and there is no way to
On Tuesday 10 December 2013 18:49:22 Dan Williams wrote:
On Tue, 2013-12-10 at 18:14 +0100, Pali Rohár wrote:
On Tuesday 10 December 2013 17:10:50 Pali Rohár wrote:
On Tuesday 10 December 2013 16:49:23 Kalle Valo wrote:
Pali Rohár pali.ro...@gmail.com writes:
Driver wl1251
Driver wl1251 generating mac address randomly at startup and there is no way to
set permanent mac address via SET_IEEE80211_PERM_ADDR. This patch export sysfs
file which can set permanent mac address by userspace helper program. Patch is
needed for devices which do not store mac address in
Driver wl1251 generating mac address randomly at startup and there is no way to
set permanent mac address via SET_IEEE80211_PERM_ADDR. This patch export sysfs
file which can set permanent mac address by userspace helper program. Patch is
needed for devices which do not store mac address in
38 matches
Mail list logo