Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-17 Thread Dmitry Smirnov
Hi Patrick, Julien

Since linux-image-3.1.0 arrived in unstable (many thanks Ben),
perhaps it would be nice if you could try it with your NIC so we learn
how well new r8169 work with your card.

Could you please provide some feedback?

Because r8168 qualifies for non-free I would like to have it there
only if none of r8169 works.
If working alternative available in newer kernels, we simply don't
need r8168 and this will suit Ben.

Thanks for http://code.google.com/p/r8168/ which seems to be right
upstream home page which I wasn't aware of.

I don't have problematic NIC so just like Andreas I can only test the
package but not the driver.

Regards,
Dmitry.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-14 Thread Andreas Beckmann
On 2011-11-13 16:59, Patrick Matthäi wrote:
 Am 13.11.2011 15:08, schrieb Andreas Beckmann:
 I just revived my old ITP http://bugs.debian.org/642198

Updated packaging is available at
git://github.com/anbe42/r8168.git

Patrick, you may want to test it. Also testing to switch back from r8168
to r8169 would be interesting.

 But btw isn't http://code.google.com/p/r8168/ the better homepage for it?

That's an unofficial mirror, so I wouldn't take it for the Homepage.
But at least we can use it for the watch file.

 [...] and I am still available to sponsor the upload :)

I still offer to maintain the package (or co-maintain it with Dmitry).
But I don't have any NIC that requires r8168 (on a quick glance I didn't
even find anything using r8169), so I can't test beyond module compilation.

If you want to see it rather in non-free than in main, please say so.


Andreas



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-13 Thread Andreas Beckmann
On 2011-11-12 19:04, Patrick Matthäi wrote:
 @Andreas and Dmitry:
 You may cooperate on packaging or decide, who wants to maintain it in
 the future.

I just revived my old ITP http://bugs.debian.org/642198
and tried to put my things in a git repository:
Only git://git.debian.org/~anbe-guest/r8168.git seems to work so far.

 @Ben:
 I still think this driver should be added as alternative driver to the
 archive, until r8169 will do its job for the promoted PCIIDs correctly.

One possible solution I see would be to upload r8168 to sid (or
experimental) and add a severity=serious bug r8168 should not enter
testing - let's fix r8169 in the kernel instead to prevent migration.
Documentation should include detailed instructions how to properly
report bugs for the in-kernel r8169 if it does not work (but r8168 does).

Do I see it correctly that this driver is to be classified as non-free?
The source code says GPL2+, but 50% of the source lines is something like
mdio_write(tp, 0x1E, 0x0078);
making this look very 'blobby'.

Andreas



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-13 Thread Ben Hutchings
On Sun, 2011-11-13 at 15:08 +0100, Andreas Beckmann wrote:
 On 2011-11-12 19:04, Patrick Matthäi wrote:
  @Andreas and Dmitry:
  You may cooperate on packaging or decide, who wants to maintain it in
  the future.
 
 I just revived my old ITP http://bugs.debian.org/642198
 and tried to put my things in a git repository:
 Only git://git.debian.org/~anbe-guest/r8168.git seems to work so far.
 
  @Ben:
  I still think this driver should be added as alternative driver to the
  archive, until r8169 will do its job for the promoted PCIIDs correctly.
 
 One possible solution I see would be to upload r8168 to sid (or
 experimental) and add a severity=serious bug r8168 should not enter
 testing - let's fix r8169 in the kernel instead to prevent migration.
 Documentation should include detailed instructions how to properly
 report bugs for the in-kernel r8169 if it does not work (but r8168 does).
 
 Do I see it correctly that this driver is to be classified as non-free?
 The source code says GPL2+, but 50% of the source lines is something like
 mdio_write(tp, 0x1E, 0x0078);
 making this look very 'blobby'.

Those sequences are reconfiguring the PHY, but some of them also patch
the PHY firmware.  Compare with the in-tree version which uses
request_firmware() for the latter.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


signature.asc
Description: This is a digitally signed message part


Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-13 Thread Patrick Matthäi

Am 13.11.2011 15:08, schrieb Andreas Beckmann:

On 2011-11-12 19:04, Patrick Matthäi wrote:

@Andreas and Dmitry:
You may cooperate on packaging or decide, who wants to maintain it in
the future.


I just revived my old ITP http://bugs.debian.org/642198
and tried to put my things in a git repository:
Only git://git.debian.org/~anbe-guest/r8168.git seems to work so far.


@Ben:
I still think this driver should be added as alternative driver to the
archive, until r8169 will do its job for the promoted PCIIDs correctly.


One possible solution I see would be to upload r8168 to sid (or
experimental) and add a severity=serious bug r8168 should not enter
testing - let's fix r8169 in the kernel instead to prevent migration.
Documentation should include detailed instructions how to properly
report bugs for the in-kernel r8169 if it does not work (but r8168 does).


I do not agree.
The package description and README should state, that it is an alternate 
driver which should be used, if r8169 does not work.

It SHOULD enter wheezy as alternative, if r8169 is still buggy.

What should be handled by upstream and what should be fixed is outside 
of this discussion and I am still available to sponsor the upload :)


But btw isn't http://code.google.com/p/r8168/ the better homepage for it?

Cheers



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#642198: Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)

2011-11-12 Thread Patrick Matthäi
Am 10.11.2011 10:42, schrieb Dmitry Smirnov:
 Package: wnpp
 Severity: wishlist
 Owner: Dmitry Smirnov only...@member.fsf.org
 
 * Package name: r8168-dkms
   Version : 8.026.00
   Upstream Author : Realtek Semiconductor Corp.
 * URL :
 http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PNid=13PFid=5Level=5Conn=4DownTypeID=3GetDown=false
 * License : GPL-2+ (contains binary blobs)
   Programming Lang: C
   Description : Realtek r8168 device driver for Linux (DKMS version)
  r8168 is the Linux device driver released for RealTek RTL8168B/8111B,
  RTL8168C/8111C, RTL8168CP/8111CP, RTL8168D/8111D, RTL8168DP/8111DP, and
  RTL8168E/8111E Gigabit Ethernet controllers with PCI-Express interface.
  .
  This is to substitute built-in r8169 driver if it doesn't work well.

I just searched this thread in my MUA and notified that Andreas Beckmann
already filled an ITP on 20.09.2011 @ #642198

@Andreas and Dmitry:
You may cooperate on packaging or decide, who wants to maintain it in
the future.

@Ben:
I still think this driver should be added as alternative driver to the
archive, until r8169 will do its job for the promoted PCIIDs correctly.

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



signature.asc
Description: OpenPGP digital signature