On Sun, 9 Sep 2007 13:13:26 +0200
Adrian Bunk <bunk@kernel.org> wrote:

quoted text
> On Sat, Sep 08, 2007 at 10:42:20PM -0400, Kyle Rose wrote:
> > 
> > > You are a regular reader of linux-kernel, and therefore the sk98lin 
> > > removal can hardly be a surprise for you. If you prefer whining over 
> > > helping to improve the kernel that's your choice...
> > >   
> > In my case the issue is simply one of practicality: I cannot go to the
> > data center 5 times per day to reboot my colo box.  Therefore, I run
> > sk98lin.  It's really that simple.
> 
> When did you report this bug the first time?
> 
> What we need is that people when testing a new kernel they plan to use 
> test the new drivers *and report the bugs if they run into any*.
> 
> What could we have done so that you reported your bug without removing 
> the sk98lin driver?
> 
> > Kyle
> 
> cu
> Adrian


There are several different problems in this thread:
1. The removal of old sk98lin driver caused some users to be forced to use
    skge. These users have uncovered issues with the dual port fiber based versions
    of the board.  
    Short term: The sk98lin driver should be restored to previous state, 
       and the PCI table should be used to limit the usage to only fiber systems.
       If Adrian doesn't do it, I'll do it when I return from Germany.
    Long term: I have fiber based board (thanks ebay) on the way to resolve
       skge bug.

2. Sky2 driver has it's own fiber based problems.  Solve these after skge fiber.

3. Sky2 doesn't have as many workarounds for hardware problems as vendor sk98lin
    driver.
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/