hi,
Support for RTL8187SE devices(0x8199) was added to
rtl8180 recently. See 1eba648f998ef9c31b8cf062754a4a7b4ab9001f
On Thu, Apr 10, 2014 at 06:21:36PM +0300, Dan Carpenter wrote:
> The thing about keeping e100 in parallel with the other driver is that
> some devices didn't work on the other driver and also it wasn't staging
> code.
>
> I don't have strong opinions either way, but if we decide to keep the
> old driver around for another kernel release "just in case" then we
> should make it print a warning on load or something to say that it's
> soon going to be removed.
No, I'll just remove it entirely, no need for it to be around at all
anymore.
thanks,
greg k-h
On Wed, Apr 09, 2014 at 10:10:49AM +0200, Xose Vazquez Perez wrote:
> hi,
>
> Support for RTL8187SE devices(0x8199) was added to
> rtl8180 recently. See 1eba648f998ef9c31b8cf062754a4a7b4ab9001f
Very nice, so, any objection to me deleting the staging driver now?
thanks,
greg k-h
I honestly can't estimate how many rtl8187se users will be gained by
this driver once it will appears in mainline (considering that most
users will probably run kernels from distributions, that updates
fairly slower than vanilla) and how much new use-cases this driver
will suddenly encounter... Assuming they are not so few, If I had to
decide, I would vote for keeping the staging driver in parallel to
rtl8180 driver for a bit..
In this way we keep a fallback alternative if someone faces any regression..
Rtl8180 driver should be enough for most users (and I hope most of
them will prefer it for a number of reasons, first of all the fact
that the staging driver here sometimes oopsed), but it is still
possible that someone will prefer to stick with staging for a while
(in my plan I will try to do some other features improvement to
rtl8180, and maybe rtl8187, drivers that indeed are present in staging
code).
AFAIK Linux have kept some alternate ethernet driver (intel e100? am I
right ?) and even two firewire stack for long time.. Maybe for staging
stuff we can strongly shorten time, but without totally clamping to
zero :)
... But about this kind of kernel decisions, I guess other people here
are by far more experienced than me.. This is just my personal humble
opinion.. Probably I already wasted too much words with it :)
BTW since the staging driver has been the only (AFAIK) source of
information about rtl8187se HW publicly available, I would like to put
a note in the rtl8180 driver main file, that indicates the latest
linux version in which the staging code could be found, as reference
for who may try to improve/debug rtl8180 driver -se support in future.
Please notify me when the staging code will be killed, and I will post
a patch for that comment note update.
Andrea
On Wed, Apr 9, 2014 at 7:08 PM, Greg KH <[email protected]> wrote:
> On Wed, Apr 09, 2014 at 10:10:49AM +0200, Xose Vazquez Perez wrote:
>> hi,
>>
>> Support for RTL8187SE devices(0x8199) was added to
>> rtl8180 recently. See 1eba648f998ef9c31b8cf062754a4a7b4ab9001f
>
> Very nice, so, any objection to me deleting the staging driver now?
>
> thanks,
>
> greg k-h
The thing about keeping e100 in parallel with the other driver is that
some devices didn't work on the other driver and also it wasn't staging
code.
I don't have strong opinions either way, but if we decide to keep the
old driver around for another kernel release "just in case" then we
should make it print a warning on load or something to say that it's
soon going to be removed.
regards,
dan carpenter