questions to Gdium patches

7 views
Skip to first unread message

Coly Li

unread,
Jun 20, 2009, 12:49:10 PM6/20/09
to One Laptop Per Hacker
These days, I am helping the GSoC student to port Loongson/Gdium
patches to openSuSE kernel.
The target kernel source is based upon 2.6.30 final, all patches I
fetched from linux-gdium branch of philv's linux-mips repository are
before 2.6.30-rc3.

I list all patches I found for Gdium in the end of this email. Here
are my questions,
1) Do I miss any patche for Gdium ?
2) If I want to apply these patches to upstream 2.6.30, do I need any
other Loongson2f patches from ralf's linux-mips tree ?

Now I am trying to apply these Gdium patches to 2.6.30, wish I am
lucky :-)

Gdium patches I found:
0001-Initial-import-of-most-of-the-Gdium-code.patch
0002-Fixed-up-some-code-added-PCI-ops.patch
0003--More-fixes-to-Loongson-2F-related-files.patch
0004-Added-missing-arch_irq_init-and-plat_irq_dispatch.patch
0005-Added-more-code-to-remove-dependence-on-bonito64.h.patch
0006-Add-the-updated-OHCI-driver-for-SM501-event.patch
0007-Added-missing-sm2d.c-file-for-the-updated-SM501.patch
0008-Various-fixes-revamped-early-printk.patch
0009-Added-default-config-for-the-Gdium.patch
0010-Added-exclusion-line-for-VGA-console-if-build-for-the-Gdium.patch
0011-More-fixes-updates-in-the-SM501-USB-driver.patch
0012-Updated-Gdium-defconfig.patch
0013-More-fixes-slight-code-restructuring-refactoring-to-eliminate-
some-magic-numbers.patch
0014-Various-cleanups-and-fixes-to-the-Gdium-support-in-2.6.29.patch
0015-Add-SM501-GPIO-expander.patch
0016-Add-the-gdium-laptop-driver.patch
0017-Various-fixes-to-the-Gdium-board-support.patch
0018-Various-bugfixes.patch
0019-Fixed-a-bone-headed-typo.patch
0020-Updated-defconfig-for-Gdium.patch
0021-Fixed-a-missing-export-for-ALSA-support.patch
0022-Added-broken-support-for-the-SM501-audio-interface.patch
0023-Initial-Gdium-Power-Managment-Support.patch
0024-Fix-compile-error-in-sm501-ALSA-SoC-driver.patch
0025-Fixed-loop-condition-bug-in-early-printk-for-Gdium.patch
0026-Add-mtd-support-for-PMON-updates.patch
0027-Removed-reference-to-v2-Gdium-boards.patch
0028-Make-Loongson-2F-PCI-highmem-default.patch
0029-Remove-unnecessary-asm-statement.patch
0030-Add-cpu-feature-overrides.h-for-Loongson-2E.patch
0031-Add-STLS2F-specific-cpu-feature-overrides.h.patch
0032-Remove-dangling-includes.patch
0033-Add-updated-cpu-feature-overrides.h-for-STLS2F.patch

Thanks in advance.

Måns Rullgård

unread,
Jun 20, 2009, 1:30:26 PM6/20/09
to gd...@googlegroups.com
Coly Li <col...@gmail.com> writes:

> These days, I am helping the GSoC student to port Loongson/Gdium
> patches to openSuSE kernel.

Wouldn't it make more sense to adapt the patches for mainline Linux?
Then any distro could apply it's specific hacks to a generic gdium
kernel, and all gdium kernel hackers could work on a common code base.
I can't imagine any reason for distros to use different gdium-specific
patches.

--
Måns Rullgård
ma...@mansr.com

Coly Li

unread,
Jun 21, 2009, 8:52:50 AM6/21/09
to One Laptop Per Hacker


On Jun 21, 1:30 am, Måns Rullgård <m...@mansr.com> wrote:
> Coly Li <col...@gmail.com> writes:
> > These days, I am helping the GSoC student to port Loongson/Gdium
> > patches to openSuSE kernel.
>
> Wouldn't it make more sense to adapt the patches for mainline Linux?

I agree with you, but the patches I found from philv's linux-mips tree
are not mainlined yet. Fortunately, it seems most of the loongson
patches are merged into 2.6.30 mainline.

> Then any distro could apply it's specific hacks to a generic gdium
> kernel, and all gdium kernel hackers could work on a common code base.
> I can't imagine any reason for distros to use different gdium-specific
> patches.
>
I agree with your opinion, though I don't find any answer to my
question ;-)

BTW, this GSoC project is porting openSuSE to MIPS platform, and the
first hardware platform is Gdium. Kernel is only <5% effort of this
project, most of efforts are in user space porting.
If these Gdium patches can be in mainline someday, it will be much
eaier for kernel compiling/building. IMHO, it should be very soon,
thanks to the loongson/gdium team for their perfect working :-)


Reply all
Reply to author
Forward
0 new messages