Hi,

On 19.11.2010, at 17:31, Jan Rovins wrote:

> 
> On 11/18/2010 2:27 PM, Jan Rovins wrote:
>> Hi,   Still trying out the x86 desktop build on 9.0.
>> 
>> I am seeing many 3rd party module build failures in the linux26 stage5 build.
>> The first one that I am getting is with sdricoh_cs.
>> 
>> The sdricoh_cs build was failing because there are many #defines that no 
>> longer work with the current kernel includes that we are using.
>> 
>> I went to the sdricoh_cs website to see if there is a newer version of their 
>> driver, and there was, but they also had the following note:
>> http://sdricohcs.sourceforge.net/:
>> "Since kernel version 2.6.27, the driver has been included in the official 
>> kernel sources from http://kernel.org.";
>> 
>> It looks like we are pulling a specific old revision directly out of their 
>> svn repository.
>> [D] X sdricoh_cs-r18.tar.bz2 
>> svn+http://sdricohcs.svn.sourceforge.net/svnroot/sdricohcs/sdricoh_cs 
>> sdricoh_cs -r18
>> 
>> We probably should remove this package from the 9.0 trunk, for 2.6 kernels 
>> and  divert anything that relies on this package to just use the module that 
>> is already in the kernel.
>> 
>> Jan
>> 
>> 
>> 
> Ok, I had a chance to look into this a little further,
> It seems that the kernel has that driver already built as a module:
> 
> CONFIG_MMC_SDRICOH_CS=m
> 
> So we just have to get rid of the old 3rd party driver in desktop/pkgsel
> 
> Index: target/desktop/pkgsel
> ===================================================================
> --- target/desktop/pkgsel       (revision 38089)
> +++ target/desktop/pkgsel       (working copy)
> @@ -463,7 +463,7 @@
> X knetconf
> 
> # other drivers
> -X sdricoh_cs
> +#X sdricoh_cs # already in the 2.6 kernel since 2.6.27


Thank you for the report, completely wiped this and the package, too:

Committed revision 38091.

        René

-- 
  René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
  http://exactcode.com | http://t2-project.org | http://rene.rebe.de

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to