I note that the file /tmp/state/network contains the interface, ip address,
and expiration time of the WAN DHCP lease... I'm wondering what's
involved in writing that information into somewhere persistent where it
can be reused on reboot?
If, for instance, a previous boot acquired a lease for x.x
I second that.
Best regards.
On Mon, Apr 4, 2011 at 11:33 PM, Layne Edwards wrote:
> On Fri, 01 Apr 2011 19:31:41 +0200, Gregers Petersen wrote:
>
> Dear all
>
> I promised to post an agenda for the patch process meeting sunday on irc
> -devel @ 19:00 UTC.
>
> The generel discussion has concern
2011/4/10 Rafał Miłecki :
> Versioning of firmware is a little tricky, because version of included
> firmware does not match version of driver. This way there is not such
> think as firmware 4.150.10.5. If you want to be strict about that, you
> can apply my following naming suggestions.
I've thou
W dniu 10 kwietnia 2011 22:50 użytkownik Jonas Gorski
napisał:
> 2011/4/10 Rafał Miłecki :
>> 2011/4/10 Jonas Gorski :
>>> Add the 5.10.56.27 firmware option. This includes updating b43-fwcutter to
>>> its newest release 14 and updating the b43-fwsquash.py to recognise rev 16
>>> n phy files.
>>
>
2011/4/10 Rafał Miłecki :
> 2011/4/10 Jonas Gorski :
>> Add the 5.10.56.27 firmware option. This includes updating b43-fwcutter to
>> its newest release 14 and updating the b43-fwsquash.py to recognise rev 16
>> n phy files.
>
> Do you maybe have any idea who is responsible for broadcom-wl-*
> pack
Versioning of firmware is a little tricky, because version of included
firmware does not match version of driver. This way there is not such
think as firmware 4.150.10.5. If you want to be strict about that, you
can apply my following naming suggestions.
2011/4/10 Jonas Gorski :
> - config
2011/4/10 Rafał Miłecki :
> 2011/4/10 Jonas Gorski :
>> Also there is no support for actual 11n, and on the TX side it is afaik
>> limited to 11M. RX should work with up to 54M.
>
> Thank you Jonas for bringing this to OpenWRT. The problem with kernel
> 2.6.38 is we don't set some config word in TX
2011/4/10 Jonas Gorski :
> Add the 5.10.56.27 firmware option. This includes updating b43-fwcutter to
> its newest release 14 and updating the b43-fwsquash.py to recognise rev 16
> n phy files.
Do you maybe have any idea who is responsible for broadcom-wl-*
packages on mirror server? I asked for u
2011/4/10 Jonas Gorski :
> Also there is no support for actual 11n, and on the TX side it is afaik
> limited to 11M. RX should work with up to 54M.
Thank you Jonas for bringing this to OpenWRT. The problem with kernel
2.6.38 is we don't set some config word in TX packet header and
firmware refuses
Since 2.6.38 b43 has initial working support for the earlier N-PHYs
(namely BCM4321 and BCM4322), I thought it would be nice to be able to use
it in OpenWrt.
These patches add a new firmware version needed for BCM4322 ucode, add
additional options to kmod-b43 (PIO and debug), and finally make N-PH
Allow enabling of N-PHY support for BCM4321 and BCM4322.
Signed-off-by: Jonas Gorski
---
package/mac80211/Makefile | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/package/mac80211/Makefile b/package/mac80211/Makefile
index 031fea2..dde3308 100644
--- a/pa
Allow reenabling the PIO mode fallback for b43.
Signed-off-by: Jonas Gorski
---
package/mac80211/Makefile | 12 ++
package/mac80211/patches/810-b43_no_pio.patch | 30 ++--
2 files changed, 29 insertions(+), 13 deletions(-)
diff --git a/package
Allow enabling debug output and debugfs for B43.
Signed-off-by: Jonas Gorski
---
package/mac80211/Makefile | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/package/mac80211/Makefile b/package/mac80211/Makefile
index c48f172..0e735dc 100644
--- a/package/mac802
Add the 5.10.56.27 firmware option. This includes updating b43-fwcutter to
its newest release 14 and updating the b43-fwsquash.py to recognise rev 16
n phy files.
Also rename the current options from STABLE/EXPERIMENTAL to their version
numbers.
Signed-off-by: Jonas Gorski
---
package/mac80211/
On 10 April 2011 17:54, David Goodenough
wrote:
> and of course the Pro uses a different switch, the AR8216.
Actually the AR8316 ;-). But similar to the ADM6996M/FC, the internal
switch registers are accessed through the MDIO interface by reading
and writing to special phy addresses.
Regards
Jon
and of course the Pro uses a different switch, the AR8216.
David
On Sunday 10 April 2011, Jonas Gorski wrote:
> On 10 April 2011 12:09, Peter Lebbing wrote:
> > So, do you have any ideas on the best way to properly handle this PHY
> > that looks like 32 PHYs?
>
> Take a look at ar71xx, they def
On 10 April 2011 12:09, Peter Lebbing wrote:
> So, do you have any ideas on the best way to properly handle this PHY that
> looks
> like 32 PHYs?
Take a look at ar71xx, they define a (machine dependent) phy mask for
each eth that says at which phy addresses a device may attach.
e.g. the rs pro
Hi,
i see there is quite a bit of interest amazon support. i will add it to
the queue, but it will take a couple of months i guess. making
pci/eth/usb work will happen, as for voice and dsl i am not sure.
John
___
openwrt-devel mailing list
openwrt-deve
Hi guys,
Normally, when you access an Ethernet PHY through an MDIO bus, you specify a
5-bit PHY address that selects one of the PHYs attached to the bus, and a 5-bit
register address that addresses a register inside that PHY.
The ADM6996FC and ADM6996M switch chips occupy this full address space:
2011/4/9 Stefan Pomaska
> max.mus...@kaffeeschluerfer.com pretended :
>
>> Thanks for you quick answer:
>>
> [...]
>
>> But of course I am aware that supporting more actual platforms has more
>> importance and maybe I am the only one with this rather old platform, but
>> afaik there used to be s
On Sun, 2011-04-10 at 01:55 +0200, Jo-Philipp Wich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi.
>
> > - Removed the avm patch, as lots of things got included in the newer
> >version and the left-over parts seemed to break samba
>
> The left over parts where stripping dow
On 08/04/11 03:20, Yeoh Chun Yeow wrote:
> You have any clue which datasheet for FC chip should be referred to. For
> me, it seems that it is not similar to F chip or not totally same with M
> chip.
I'd love to have a datasheet for the FC chip, but I can't find it.
It would appear the M is an en
22 matches
Mail list logo
