Francois Romieu wrote:

Jens Stroebel [off-list ref] :
[...]

quoted

Would it
be possible to apply the single patch to 2.6.21.5 and get a working
driver?

Mantra: mainline first, stable later.

hm .. OK.

In the next future, most of this patchset will hopefully go into
2.6.23-rc1. Some people will then complain that 2.6.23-rc1 breaks
their 816x. After that the patchkit will be amended and the r8169
regressions in 2.6.23-rcX fixed.

Then it will be time to feed some r8169 bits in 2.6.2x.y

By this time, probably the hosts which should run w. the driver will be
standing all around the world, which makes applying a patch slightly
more interesting... ;-)

But see below:

It may help and/or accelerate things if you can narrow the fix(es) in
the current r8169 serie.

As I mentioned in the initial message, I had experimented with
2.6.22rc6; unfortunately

 a) we have some stuff depending on the kernel where
    2.6.21.5<->2.6.22rc6 makes a difference (does not work)
 b) I experienced a hard lockup w. kernel 2.6.22rc6 this morning while
    not really doing something special (file IO, extracting a tar. As
    this was reproducably happening, we retreated from experimenting
    with it now.

Instead, I built 2.6.21.5+[a patch I snatched from a mail communication
you had on 2007-06-20
(Msg-ID: [ref] )].
I will attach it with this mail, as it is really small and you don't
have to dig around to know what I'm talking about.

As I am no kernel-developer, I am not sure there are no undesired side
effects by applying this patch to this kernel; if you think there are
(could/should be), it would be nice if you could state that, so I'd
refrain from testing with this combination.

		greets,
		   jens
-- 
drifter@bcsoft.de
			23.....56.......drifting
By caffeine alone I set my mind in motion, By the beans of Java
do thoughts acquire speed,  hands acquire shaking,  the shaking
becomes a warning, By caffeine alone do I set my mind in motion