Hi, Peter,
Thanks for you explanation. I have learned some insights on how the PHY/MAC
works and MII.
FYI, the patch works. I have tested with following /etc/config/network to
send out the tagged packet:
config 'switch'
option 'name' 'eth1'
option 'reset' '1'
option 'enab
Please also note that the real time clock is important for knowing if
the DHCP lease is still valid.
Since most routers don't have a hardware RTC, there is no way to know
it the DHCP lease is still valid before you get WAN connectivity to
update the time with NTP.
Nuno
On Tue, Apr 12, 2011 at 05:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
can you resend the patches as one big one?
svn diff package/feeds/packages/iftop/{Makefile,patches} \
> iftop-update.patch
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
is this patch still applicable after
https://dev.openwrt.org/changeset/26426 ?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2kti0ACgkQdputY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
patching file scripts/feeds
Hunk #1 FAILED at 106.
Hunk #2 FAILED at 283.
2 out of 2 hunks FAILED -- saving rejects to file scripts/feeds.rej
Can you rebase your patch?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comm
On 04/12/2011 12:02 AM, Rafał Miłecki wrote:
> W dniu 11 kwietnia 2011 00:32 użytkownik Jonas Gorski
> napisał:
>> 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
>>> thin
I'm getting "invalid block reference" errors when booting the VDI image.
Also, / is mounted read-only whereas in backfire it was mounted
read-write. I think the 2 might be related. Any ideas?
- Ryan
___
openwrt-devel mailing list
openwrt-devel@lists.op
Hi,
I hopefully have finished the two versions of the driver. One effectively only
supports the M model (though it detects and initialises the FC model), and the
second experimental one adds VLAN support for the FC model.
I don't have the time right now to do the official patch submission. But
at
- this configuration option seems to be undocumented. Unfortunately,
it tries to disable powersaving by default for all mac80211 based
wifi interfaces that use 'sta' mode. Some drivers (e.g. ath5k) don't
support setting/enabling powersaving mode. The result is an error
message when bringing
Hi,
I am getting the following error when bringing up ath5k:
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not supported.
The patch that follows proposes a potention solution to this. I am
assuming the original version uses iwconfig instead
Dear Slawomir Cygan,
Thanks for your response.
2011/4/12 Sławomir Cygan :
> So now you are using jtag - You mentioned gdbserver in last post, so
> my last response won't apply to Your problem. Please refer to your
> jtag hardware and software documentation for more help.
> You also did not mentio
So now you are using jtag - You mentioned gdbserver in last post, so
my last response won't apply to Your problem. Please refer to your
jtag hardware and software documentation for more help.
You also did not mention in last post that You are trying debug the
kernel - if so, build it with debug inf
Dear Slawomir Cygan,
Thank you very much for your infromation.
2011/4/12 Sławomir Cygan :
> Hi,
>
>> We are unable to debug the OpenWRT image through GDB from a host
>> system. When we try to debug, we are seeing the following error
>> messages on the GDB screen. We are running the GDB from Cygwi
2011.04.11. 6:33 keltezéssel, Jonas Gorski írta:
> Add support for the Buffalo WZR-HP-G301NH. The only difference between it
> and the WZR-HP-G00NH is that it has a RTL8366RB instead of a RTL8366S.
> Since we don't do runtime detection of the switch, we need a separate
> machine definition for it.
2011.04.08. 21:52 keltezéssel, Jonas Gorski írta:
> Since the PHY driver is only used for the WAN port and there is virtually
> no difference between it and the generic PHY driver, we can sefely remove
> it.
>
> Signed-off-by: Jonas Gorski
Applied in r26600.
Thanks,
Gabor
__
On 12/04/11 09:15, Yeoh Chun Yeow wrote:
> Unfortunately, the driver that you provided not able to detect the
> switch correctly "ADM6996FC PHY detected".
>
> I have observed the following:
> eth0: PHY overlaps ADM6996, providing fixed PHY 14.
> eth1: PHY overlaps ADM6996, providing fixed PHY 10.
Unfortunately, the driver that you provided not able to detect the switch
correctly "ADM6996FC PHY detected".
I have observed the following:
eth0: Atheros AG71xx at 0xb900, irq 4*
eth0: PHY overlaps ADM6996, providing fixed PHY 14.*
eth0: connected to PHY at ag71xx-mdio:14 [uid=1027, driv
17 matches
Mail list logo
