re(4) resync. Adds preliminary support for 8168G, 8168EP, 8168GU, 8411B and 8106EUS.

[Yonghyeon PYUN]

On Mon, Oct 28, 2013 at 03:11:00PM +0900, Yonghyeon PYUN wrote:
> On Mon, Oct 28, 2013 at 04:48:35PM +1100, Edward O'Callaghan wrote:
> > On Mon, 28 Oct 2013 11:27:23 +0900
> > Yonghyeon PYUN <pyunyh at gmail.com> wrote:
> > 
> > > On Sun, Oct 27, 2013 at 11:13:25PM +1100, Edward O'Callaghan wrote:
> > > > Hi,
> > > > 
> > > > This is a follow up. I have tested most of these NIC's now and this
> > > > patch _should_ be fine to commit to HEAD. Could someone please help
> > > > me mediate this? This also fixes kern/183167. Please disregards the
> > > > patches in the PR.
> > > > 
> > > 
> > > I can handle this. Actually I had been working on supporting these
> > > newer controllers for a while. It seems just adding 8168GU id does
> > > not work. Did you test the patch on 8168GU controller?
> > > If yes, please let me know the OUI id and model number of the PHY.
> > 
> > Hi Yonghyeon,
> > 
> > Many thanks! Not the 8168GU, however I did find out that its the same
> > as a 8106EUS. I don't know if this may shed some light if you have the
> > hw to test it.. What exactly did not work about the 8168GU, what is it
> > doing?
> 
> Intermittent packet drops and slightly high number of RX
> interrupts.
> 
> > 
> > My main concern is to get a board here working that has a 8168G onboard.
> > 
> 
> Just adding RTL8168G id would use ukpky(4). Probably rgephy(4)
> should be taught to pick up the PHY but I don't have copy of data
> sheet. I'm testing patched rgephy(4) at this moment so give me some
> time.
> 

FYI: Committed in r257304-257306.
These commits do not address high number of RX interrupts though.