2010/11/22 包孟謙 <bao.mengq...@gmail.com>:
> On Mon, Nov 22, 2010 at 2:34 AM, wu zhangjin <wuzhang...@gmail.com> wrote:
>>
>> Hi, Julien
>>
>> On Mon, Nov 22, 2010 at 1:15 AM, julien forgeat <julienforg...@gmail.com>
>> wrote:
>> > On Mon, Nov 15, 2010 at 10:53 AM, wu zhangjin <wuzhang...@gmail.com>
>> > wrote:
>> >> On Mon, Nov 15, 2010 at 5:11 AM,  <bao.mengq...@gmail.com> wrote:
>> >>> Once again: thanks a lot, this is great news!
>> >>>
>> >>> Since your last update I have been busy rolling kernels with the
>> >>> updated sources but soon suspended my efforts when I felt that the
>> >>> Gdium was overheating due to lm_sensors not being functional and thus
>> >>> fancontrol not operating the fan.
>> >>>
>> >>>
>> >>> One question remains: now that the 'master' branch has been updated
>> >>> with improved gdium support, is the 'gdium' branch deprecated?
>> >>>
>> >>
>> >> Yes, I will drop the /dev/gdium branch.
>> >>
>> >> Regards,
>> >> Wu Zhangjin
>> >>
>> >>>
>> >>> On 01:12 15 Nov 10, wu zhangjin wrote:
>> >>>> Hi, all
>> >>>>
>> >>>> New status of linux-loongson-community for Gdium:
>> >>>>
>> >>>> Sensors, Backlight, Function/Hotkey, AC/battery drivers work with
>> >>>> arch/mips/configs/gdium_small_defconfig, but sound and pm/suspend
>> >>>> still not work.
>> >>>>
>> >>>> 1. Sensors
>> >>>>
>> >>>> lm75 driver must be enabled as y or m, then you can use 'sensors'
>> >>>> command to get the board(or cpu? not sure) temperature.
>> >>>>
>> >>>> 2. Backlight
>> >>>>
>> >>>> pwm_backlight common driver(CONFIG_BACKLIGHT_PWM) must be enabled as
>> >>>> y
>> >>>> or m, then you can use kpowersave or gnome-power-manager to change
>> >>>> the
>> >>>> backlight, or you can use the interface
>> >>>> /sys/class/backlight/pwm-backlight/brightness directly.
>> >>>>
>> >>>> 3. Function/Hotkey drivers(include hid-gdium and gdium_laptop)
>> >>>>
>> >>>> All of the Fn key should work now(except the ones for the volume/mute
>> >>>> changing).
>> >>>>
>> >>>> CONFIG_HID_GDIUM and CONFIG_GDIUM_LAPTOP must be enabled as y or m.
>> >>>>
>> >>>> With the help of function key, you can change the backlight via
>> >>>> Fn+F8/F9.
>> >>>>
>> >>>> More function key maps are defined as follows:
>> >>>>
>> >>>> drivers/hid/hid-gdium.c:
>> >>>>
>> >>>>         { KEY_F1,       KEY_CAMERA },
>> >>>>         { KEY_F2,       KEY_CONNECT },
>> >>>>         { KEY_F3,       KEY_MUTE },
>> >>>>         { KEY_F4,       KEY_VOLUMEUP},
>> >>>>         { KEY_F5,       KEY_VOLUMEDOWN },
>> >>>>         { KEY_F6,       KEY_SWITCHVIDEOMODE },
>> >>>>         { KEY_F7,       KEY_F19 }, /* F7+12. Have to use existant
>> >>>> keycodes */
>> >>>>         { KEY_F8,       KEY_BRIGHTNESSUP },
>> >>>>         { KEY_F9,       KEY_BRIGHTNESSDOWN },
>> >>>>         { KEY_F10,      KEY_SLEEP },
>> >>>>         { KEY_F11,      KEY_PROG1 },
>> >>>>         { KEY_F12,      KEY_PROG2 },
>> >>>>         { KEY_UP,       KEY_PAGEUP },
>> >>>>         { KEY_DOWN,     KEY_PAGEDOWN },
>> >>>>         { KEY_INSERT,   KEY_NUMLOCK },
>> >>>>         { KEY_DELETE,   KEY_SCROLLLOCK },
>> >>>>         { KEY_T,        KEY_STOPCD },
>> >>>>         { KEY_F,        KEY_PREVIOUSSONG },
>> >>>>         { KEY_H,        KEY_NEXTSONG },
>> >>>>         { KEY_G,        KEY_PLAYPAUSE },
>> >>>>
>> >>>> 4. AC/Battery driver
>> >>>>
>> >>>> gdium_laptop also provides a AC/battery driver, which can be used to
>> >>>> monitor the AC/Battery working status, but the battery driver need to
>> >>>> be improved to provide the information of
>> >>>> POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW and
>> >>>> POWER_SUPPLY_PROP_TIME_TO_FULL_NOW, I have done some statistic on the
>> >>>> time to empty and full, will get a formula for it later.
>> >>>>
>> >>>> -------------
>> >>>>
>> >>>> BTW:
>> >>>>
>> >>>> 1. I have no time to work on the left sound and pm drivers in the
>> >>>> next
>> >>>> 2 or 3 months, so, If you folks have interest or time, welcome your
>> >>>> patches, thanks in advance.
>> >>>>
>> >>>> 2. Some notes to forward-port the sound and pm drivers:
>> >>>>
>> >>>> 2.1. sound driver
>> >>>>
>> >>>> may need to port the following three patches:
>> >>>>
>> >>>> SM501 ASoC driver    // You can search these patches after issuing
>> >>>> "git log", the same to the following ones
>> >>>> gdium_sound_fixes.patch
>> >>>> GB36_sm502_mfd_rewrite.patch
>> >>>>
>> >>>> from
>> >>>>
>> >>>> git://git.opensde.net/users/amery/linux-2.6.29-gdium
>> >>>>
>> >>>> But simply copy them from the above git repo to our git repo will not
>> >>>> work for the mainline has changed some sound APIs, please refer to
>> >>>> the
>> >>>> "ASoC: multi-component - ASoC Multi-Component Support" commit of the
>> >>>> mainline and the other implementations under sound/soc/
>> >>>>
>> >>>> 2.2 pm/suspend driver
>> >>>>
>> >>>> may need to port "stl2_suspend2.patch" from
>> >>>> git://git.opensde.net/users/amery/linux-2.6.29-gdium, but please
>> >>>> check
>> >>>> the potential conflict between it and the mainline:
>> >>>> arch/mips/loongson/common/pm.c, arch/mips/power/
>> >>>>
>> >>>> And to enable the cpufreq driver support for Gdium, the sm501-pwm
>> >>>> based external timer should be enabled, therefore, we may need to
>> >>>> port
>> >>>> "gdium_clock.patch", to make it work normally with cpufreq, its
>> >>>> oneshot mode must be fixed at first.
>> >>>>
>> >>>> Best Regards,
>> >>>> Wu Zhangjin
>> >>>>
>> >>>> On Tue, Nov 9, 2010 at 1:08 PM, wu zhangjin <wuzhang...@gmail.com>
>> >>>> wrote:
>> >>>> > Hi, mengqian & all
>> >>>> >
>> >>>> > Sorry for my late response.
>> >>>> >
>> >>>> > Based on the previous work of Arnaud Patard[1] and Yajin[2], just
>> >>>> > finished a basic 2.6.37 support(pci, irq, reset, video) for Gdium
>> >>>> > and
>> >>>> > pushed it into our master branch[3], two default config files has
>> >>>> > been
>> >>>> > added:
>> >>>> >
>> >>>> > arch/mips/configs/gdium_{minimal,small}_defconfig
>> >>>> >
>> >>>> > The minimal one is prepared for the rescue/recover system, the
>> >>>> > small
>> >>>> > one can be used for desktop or development.
>> >>>> >
>> >>>> > With anyone of the above config files, the kernel is bootable, the
>> >>>> > later enabled more supports(wireless), if you need more drivers,
>> >>>> > please refer to arch/mips/configs/lemote2f_defconfig.
>> >>>> >
>> >>>> > To boot the kernel, you may need to install the modules into the
>> >>>> > board's /lib/modules and copy the vmlinuz or vmlinux to the board's
>> >>>> > /boot, and then, config the pmon(bootloader) environment variables
>> >>>> > and
>> >>>> > boot with the new kernel:
>> >>>> >
>> >>>> > 1. Enter into the PMON commandline
>> >>>> >
>> >>>> > power on your board, and press the 'C' key till you get the
>> >>>> > following prompt.
>> >>>> >
>> >>>> > PMON>
>> >>>> >
>> >>>> > 2. Set the path to the kernel image in the "al" environment
>> >>>> > variable
>> >>>> >
>> >>>> > // take a look at the existing environment variables
>> >>>> > PMON> env
>> >>>> > // or take a look at an indicated environment variable: al
>> >>>> > PMON> env al
>> >>>> > // backup the old al
>> >>>> > PMON> set old_al $al
>> >>>> > // set the new al, assume your kernel image(vmlinuz-2.6.37) is put
>> >>>> > at
>> >>>> > the 2nd partition of your usb storage
>> >>>> > PMON> set al /dev/fs/e...@usbg0/boot/vmlinuz-2.6.37
>> >>>> >
>> >>>> > 3. Set the kernel command line parameters in "karg"
>> >>>> >
>> >>>> > PMON> env karg
>> >>>> > PMON> set old_karg $karg
>> >>>> > // Assume your root filesystem is at the 2nd partition of your usb
>> >>>> > storage
>> >>>> > PMON> set kargs "console=tty1 root=/dev/sda2 rootwait
>> >>>> > init=/sbin/finit-mdv"
>> >>>> >
>> >>>> > 4. Load & Boot
>> >>>> >
>> >>>> > // Load the kernel image
>> >>>> > PMON> load $al
>> >>>> > // Boot it
>> >>>> > PMON> g $karg
>> >>>> >
>> >>>> > If you want to load a kernel image from the tftp server, please
>> >>>> > enable
>> >>>> > the network connection via the bootloader at first.
>> >>>> >
>> >>>> > PMON> devls
>> >>>> > ...
>> >>>> > rtl0
>> >>>> > PMON> set ifconfig rtl0:<local_ip_addresss> // for example: set
>> >>>> > ifconfig rtl0:192.168.0.131
>> >>>> > PMON> load tftp://<tftp_server_ip_address>/path/to/tftpboot/vmlinuz
>> >>>> > ....
>> >>>> >
>> >>>> > To get more information about gdium, PMON and the available systems
>> >>>> > on
>> >>>> > it, please refer to [4].
>> >>>> >
>> >>>> > More efforts are needed to forward-port the following supports from
>> >>>> > 2.6.29[3] to 2.6.37:
>> >>>> >
>> >>>> > The EC support(hotkey, battery ...) from
>> >>>> > drivers/platform/mips/gdium-laptop.c (seems no big change)
>> >>>> > The sm501 based sound support from sound/soc/sm501 (may need enough
>> >>>> > effort for the mainline has changed a lot)
>> >>>> > The pm support(mainly "suspend to RAM") from
>> >>>> > arch/mips/lemote/lm2f/*pm* (stl2_suspend2.patch, this may be hard
>> >>>> > too
>> >>>> > but should be easy for basic pm support, the Hibernation should be
>> >>>> > usable currently.)
>> >>>> >
>> >>>> > Currently, I have no schedule to work on them, but I hope they may
>> >>>> > be
>> >>>> > available one by one in the coming 3 ~ 6 weeks, which means 2.6.37
>> >>>> > in
>> >>>> > our linux-loongson-community git repository.
>> >>>> >
>> >>>> > Best Regards,
>> >>>> > Wu Zhangjin
>> >>>> > ------
>> >>>> > [1] git://git.opensde.net/users/amery/linux-2.6.29-gdium
>> >>>> > [2] http://repo.or.cz/w/linux-2.6/linux-mips/linux-gdium.git
>> >>>> > (2.6.35-rc2)
>> >>>> > [3] http://dev.lemote.com/code/linux-loongson-community
>> >>>> > [4] More
>> >>>> > [4.1] FAQ
>> >>>> > http://www.gdium.com/en/support/faq
>> >>>> > [4.2] How to Install Debian Lenny on Gdium
>> >>>> >
>> >>>> > http://vm-kernel.org/blog/2009/03/20/how-to-install-debian-lenny-on-gdium/
>> >>>> > [4.3] PMON
>> >>>> > http://olph.gdium.com/wiki/doku.php/system:pmon
>> >>>> >
>> >>>> > On Wed, Oct 20, 2010 at 7:34 PM, 包孟謙 <bao.mengq...@gmail.com>
>> >>>> > wrote:
>> >>>> >> This is a question mainly for Gdium owners, but all input is
>> >>>> >> welcome.
>> >>>> >>
>> >>>> >> Did anyone successfully manage to (compile and) run a more recent
>> >>>> >> kernel thatn 2.6.29... (from Mandriva's G-linux) on his/her Gdium?
>> >>>> >>
>> >>>> >> Even if proper support for audio and hotkeys is not ported, I am
>> >>>> >> considering compiling a kernel from newer sources so I could
>> >>>> >> update
>> >>>> >> udev, include Huawei K3765 support, etc.
>> >>>> >>
>> >>>> >> In theory, I believe, the Yeelong sources should be compatible
>> >>>> >> (except
>> >>>> >> for the Gdium specific hotkeys, audio). The Gdium lacks the VIA
>> >>>> >> southbridge but I do not think that should be a problem.
>> >>>> >>
>> >>>> >> Does anyone have any experience with experimenting with "Yeelong"
>> >>>> >> kernels on the Gdium?
>> >>>> >>
>> >>>> >> Please let me know.
>> >>>> >>
>> >>>> >> --
>> >
>> > Hi Zhangjin and others.
>> >
>> > Many many thanks for working on a new kernel for the Gdium, I just
>> > gave it a try this evening and managed to get Squeeze running with
>> > LXDE without any effort.
>> >
>> > Just for the reference, here is how I proceeded:
>> >  (1) from an old Debian Lenny image, install debootstrap and
>> > deboostrap Squeeze into a new GKey
>> >  (2) chroot into the deboostraped Squeeze install build-essential and
>> > git
>> >  (3) clone master
>> >  (4) copy the small config file for the Gdium into .config
>> >  (5) follow instructions to compile and install
>> >  (6) edit a few text files: /etc/fstab and /etc/host, give a password to
>> > root
>> >  (7) quit and boot on the Squeeze GKey and install lxde-desktop
>> >
>> > Is there anything wrong with this? I am not really familiar with this
>> > kind of work, I used to install the .deb kernel package from Phil..
>> >
>>
>> Yeah, it looks good, but if you don't want to install the debian
>> yourself(save time...), you may try the pre-installed one contributed
>> by Shiwei: http://www.bjlx.org.cn/loongson/install/
>>
>> I have tried the lxde and gnome version, both of them run without any
>> problem. of course, no kernel image there, you still need to compile
>> one yourself. To install the pre-installed one there, you just need to
>> decompress the latest lzma package into your spare partition or
>> another Gkey.
>>
>> > The only thing I have to report is that while installing lxde, 2
>> > packages complained about the kernel not supporting multicast
>> > networking, is it something that should be changed in the config file?
>> >
>>
>> Yeah, you may need to enable more options for the small defconfig may
>> miss some important options.
>>
>> arch/mips/configs/lemote2f_defconfig is a good reference for you.
>>
>> > Will keep playing with the system, please let me know if you need
>> > anything tested and thanks again
>>
>> Playing with it is the best test, thanks and welcome your bug reports.
>> perhaps you can help to use the Fn keys(Fn+....) and the power
>> manager, wifi, backlight.... you need to install gnome-power-manager
>> of kpowersave(not sure which one does lxde has) to ensure the Fn key
>> works.
>>
>> I finally managed to make loongson2_cpufreq driver work with the R4K
>> Timer, but need to tune some parameter to ensure the Timer works
>> without big offset. after finish it, will put it into our git repo.
>> The cpufreq driver is very important to ensure the machine is not too
>> hot, after trying it on my Gdium, the temperature monitored is about
>> 53 C. but without this, it may be 65 or higher... With the help of
>> cpufreq, the notebook will be at least usable.
>>
>> And BTW, currently, the battery driver can work well with the
>> gnome-power-manager, it can report the time to empty now ;-)
>>
>> And Next, I will try PM(Suspend to disk and Memory) at first, and at
>> last, the audio/sound support.
>>
>> Thanks & Regards,
>> Wu Zhangjin
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "loongson-dev" group.
>> To post to this group, send email to loongson-...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> loongson-dev+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/loongson-dev?hl=en.
>>
>
> This paragraph is just written to set the tone for the rest message below.
> Thanks for your efforts on prepping the 2.6.37-rc1+ sources for the Gdium.
> Please take the rest of this message not as a criticism but a genuine
> wondering and a 'pre-bug report'-report ;)

This is welcome and thanks!

> So, I suppose I am alone in the problem with wifi using the latest Master
> sources? The clock keeps the time, temperature sensors function alright but
> I can not get my wifi to connect. Neither the built-in RaLink chip (rt61pci)
> nor a Linksys USB dongle (rt73usb). The interface seems down, no matter if I
> press the kill button or not, or whether I echo "0" or "1" to
> /sys/class/rfkill/rfkill0/state (this path is written from memory, so it may
> not be completely correct).

I didn't test this before for I have no wireless AP. perhaps I should
buy one this weekend ;-)

I'm not sure if I need to add Gdium specific support for rt61pci, I
will check the opensde git repo.

> Also, one of the USB drivers (I think the OHCI) is throwing "-62" errors,
> although I have not yet found any real trouble originating from this.
> For the above, I suppose logs will be greatly appreciated - just dmesg and
> /var/log/messages?

I got this error too and found it was not urgent, so no log needed, I
will check it. thanks all the same.

> Another thing is that there is some corruption of the command line whenever
> some commands are recalled from bash's history. The font becomes unreadable
> at times, but only near the cursor: the rest of the screen is ok. Perhaps a
> framebuffer screendump or something is useful?

Do you mean CRTL+R? Seems I got similar problem when I was using the
gnome terminal, when I issued something, it just hung and only
returned after several seconds. I used the fbdev X driver.

> btw my Gdium runs Gentoo, with some support of the loongson overlay (mainly
> C libraries and the toolchain).

BTW, which X driver are you using? fbdev or siliconmotion?

Thanks & Regards,
Wu Zhangjin

-- 
You received this message because you are subscribed to the Google Groups 
"loongson-dev" group.
To post to this group, send email to loongson-...@googlegroups.com.
To unsubscribe from this group, send email to 
loongson-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/loongson-dev?hl=en.

Reply via email to