public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Corentin Chary <corentincj@iksaif.net>,
	acpi4asus-user@lists.sourceforge.net
Subject: Re: Turning off camera also kills card reader on EeePC 900
Date: Wed, 17 Sep 2008 19:04:08 +0100	[thread overview]
Message-ID: <48D14698.60601@yahoo.com> (raw)
In-Reply-To: <fa.Pwdn/v9TPDX5WUUVn7K6FAfABEg@ifi.uio.no>

> Alan Jenkins wrote:
>> Sitsofe Wheeler wrote:
>>>
>>> Alan Jenkins wrote:
>>>
>>>> - It might be necessary to compare with the pre-installed OS
>>>>  - Is the pre-installed kernel any better (files might be under
>>>> /proc/acpi/asus instead)?  I guess you might not have the time or
>>>> resources to test that though.
>>>
>>> The Xandros 2.6.21.4-eeepc install has the following files in 
>>> /proc/acpi/asus/
>>> brn camera cardr cpufv disp hdps init type wlan
>>>
>>> I have no idea what cpufv, disp, hdps, init or type are. Doing echo 1 
>>> > camera && echo 0 > camera under this setup does NOT disappear the 
>>> SD card.
>> Rats.  So there is some secret the mainline driver is missing :-(.

So I got around to downloading those my 4 pieces of rar and poking about 
the source. For those who are curious inside the rars is a tar.bz2 file 
of a tree of .debs. A few hints:

DON'T download the source from China if you aren't in China it's very slow.
The global mirrors are hidden behind javascript for some reason whereas 
the Chinese ones are not. Still don't be tempted if you aren't in Japan 
- the downloads were frequently crawling along at less than 
10Kbyte/second and would periodically disconnect themselves.

The bad news for me is that part4 of the .rar archive was always corrupt 
(I redownloaded it and it was still corrupt). The good news is that I 
was able to extract some of the archive.

Here are the much faster links that worked for me:
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part1.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part2.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part3.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part4.rar

MD5SUMs of the good pieces of the above:
48bf55be427b279abfc641c10fe4b0ef  Eee_PC_900_source_code_part1.rar
56f8f02cf601c6d82fe4ef824e0b5625  Eee_PC_900_source_code_part2.rar
560d151a90b70b5edabdd9f70cfe7567  Eee_PC_900_source_code_part3.rar

SHA1SUMs of the good pieces of the above:
e6983951b556456677b4d5a77608bc117f3ffe91  Eee_PC_900_source_code_part1.rar
04ec1d1af1014f87ad54476882428ed5090f1742  Eee_PC_900_source_code_part2.rar
09d3b4c1f5356b068d4bfdf4c51dc481b53c5661  Eee_PC_900_source_code_part3.rar

In the linux-source deb there is a folder which contains patches against 
2.6.21.4. For short term convenience I have temporarily repackaged the 
patches here: 
http://sucs.org/~sits/test/eeepc-900/eeepc-kernel-patches.tar.gz 
(contains ALSA patches for the realtek intel_hda, the elantech touchpad 
driver, a pci message patch(?), huawei_usb_storage storage patch (?), 
unionfs patches and aufs patches and a kernel config file).

There is also a separate asus-acpi deb which I have temporarily repacked 
on http://sucs.org/~sits/test/eeepc-900/asus-acpi-p9xx_1.2-1_i386.tar.gz 
. Sadly it seems to contain a prebuilt asus_acpi.ko in /lib/modules 
(along with various scripts to respond to hotkeys etc).

       reply	other threads:[~2008-09-17 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.DzjC5FQ8ty+cqmv5KG/NRpAWgdE@ifi.uio.no>
     [not found] ` <fa.+Dv7n0Sa7hzDrReJcnf4HgYqsoA@ifi.uio.no>
     [not found]   ` <fa.+GChIGFRZ5au1CMIOZvlKhwFPrU@ifi.uio.no>
     [not found]     ` <fa.jNQrULYfenJPvj20234NL8Nt+cM@ifi.uio.no>
     [not found]       ` <fa.QFFph3ZzzmbGalzypmWpsSRfEPY@ifi.uio.no>
     [not found]         ` <fa.Pwdn/v9TPDX5WUUVn7K6FAfABEg@ifi.uio.no>
2008-09-17 18:04           ` Sitsofe Wheeler [this message]
2008-09-25 20:49 Turning off camera also kills card reader on EeePC 900 Sitsofe Wheeler
2008-09-26 10:56 ` Pascal Terjan
2008-09-26 13:26   ` Pascal Terjan
     [not found] <fa.ynuVPnbW9HmrQpG9wbWk/u+hqkw@ifi.uio.no>
     [not found] ` <fa.HT4htA0oryTT1h7ADNggfgkJnyY@ifi.uio.no>
     [not found]   ` <fa.5D0cM9TkJ80O2GfXhZm3n4hc+GI@ifi.uio.no>
     [not found]     ` <fa.1xyAj/9KUcq9nDwCEVhSHc5KBBs@ifi.uio.no>
     [not found]       ` <fa.jr7R0e2XSjOS0yWom34xSWH95yM@ifi.uio.no>
2008-09-15 21:41         ` Sitsofe Wheeler
     [not found] <fa.AGK4P0BJyB1JXP0f1hBx9GtBh+c@ifi.uio.no>
     [not found] ` <fa.ifmgGzvpZjuOrzmMPG9PMGHUVn4@ifi.uio.no>
     [not found]   ` <fa.jeJ+IlDCDZAKTug+iVXTMjdMIyk@ifi.uio.no>
2008-09-15 15:02     ` Sitsofe Wheeler
2008-09-15 19:42       ` Alan Jenkins
  -- strict thread matches above, loose matches on Subject: below --
2008-09-15  8:48 Alan Jenkins
2008-09-15 12:19 ` Sitsofe Wheeler
2008-09-15 13:37   ` Alan Jenkins
2008-09-25 20:27     ` Pascal Terjan
2008-09-25 21:21       ` Alan Jenkins
2008-09-26 14:47       ` Karl Kiniger
2008-09-14 16:05 Sitsofe Wheeler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48D14698.60601@yahoo.com \
    --to=sitsofe@yahoo.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=corentincj@iksaif.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox