Re: [PATCH] e1000: supply interface speed / duplex when no link-beat

2005-11-21 Thread Jesse Brandeburg
On 11/21/05, Martin Josefsson <[EMAIL PROTECTED]> wrote: > > Why do you need this? Basically this was a design decision in our > > driver to not report link when we haven't had a chance to initialize > > it (when the interface is brought up) > > If I configure an interface to disable autonegotiat

Re: [PATCH] e1000: supply interface speed / duplex when no link-beat

2005-11-21 Thread Martin Josefsson
On Mon, 2005-11-21 at 10:12 -0800, Jesse Brandeburg wrote: > Hi, thanks for the input. I have a couple of questions. Hi Jesse > Why do you need this? Basically this was a design decision in our > driver to not report link when we haven't had a chance to initialize > it (when the interface is b

Re: [PATCH] e1000: supply interface speed / duplex when no link-beat

2005-11-21 Thread Jesse Brandeburg
On 11/18/05, Martin Josefsson <[EMAIL PROTECTED]> wrote: > Currently the e1000 driver only supplies the active link speed / duplex > when a link-beat is present to ethtool. This patch adds support for > supplying the configured speed / duplex when auto-negotiation is > disabled and no link-beat is

[PATCH] e1000: supply interface speed / duplex when no link-beat

2005-11-18 Thread Martin Josefsson
Currently the e1000 driver only supplies the active link speed / duplex when a link-beat is present to ethtool. This patch adds support for supplying the configured speed / duplex when auto-negotiation is disabled and no link-beat is present. Signed-off-by: Martin Josefsson <[EMAIL PROTECTED]> --