| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
include/linux/sched.h has two copies of these credentials now... real
and effective held in two struct creds. I chose real cred but I am uncertain
it's the desired one.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=445395c9fcfb78ea62ab5a69b84c2c12efe01cff
pcf50606_rebase_changes,patch
This patch brings into andy-tracking all changes related to pcf50606 from old
balaji-tracking.
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=57b3df284f5a79346f2b25003f76c6702cf84c25
pcf50633_rebase_changes.patch
This patch brings all changes from balaji-tracking originally intended for
upstream into andy-tracking.
|
|
On Wed, Jan 21, 2009 at 08:51:41PM +0000, Andy Green wrote:
> Today I got Ben Dooks to uplevel his tree to 29-rc1, I am rebasing it
> tonight, but ssh access to git.openmoko.org git:// is broken right now.
>
Oh, I forgot! Then you might encounter the pcf50633 driver from upstream
which has lots of differences from what we have on andy-tracking. So,
here I'm attaching a patch that applies to current andy-tracking which
is how the pcf50633/mach-gta02.c should look like after rebase. You can
probaly look into it in case of confusion..
Or you can apply it before rebase ? Probably you can..
Hope it helps,
Balaji
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-fix-stray-endmenu-patch-1232632040-1232632141
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040-1232632141 / fdf777a63bcb59e0dfd78bfe2c6242e01f6d4eb9 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040
stable-tracking-hist top was MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 / 90463bfd2d5a3c8b52f6e6d71024a00e052b0ced ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-fix-stray-endmenu-patch
mokopatches-tracking-hist top was fix-stray-endmenu-patch / 3630e0be570de8057e7f8d2fe501ed353cdf34e6 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-stray-endmenu.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Allow the GPS module to be powered during suspend so it can keep the fix.
This has to be enabled by writing 1 to .../neo1973-pm-gps.0/keep_on_in_suspend
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
kernel-build-1232567797
pending-tracking-hist top was MERGE-via-stable-tracking-glamo-don-t-break-kernel-build-1232567797 / d9aa2ec4d0f11979eb9894dbcf0c1639e73a7587 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-glamo-don-t-break-kernel-build
stable-tracking-hist top was glamo-don-t-break-kernel-build / 1796c97b437a7bb998c489caba09a026bbb16564 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
Glamo: don't break kernel build if disabled
If we disable CONFIG_MFD_GLAMO, a dependency on glamo_lcm_reset from
arch/arm/mach-s3c2440/mach-gta02.c:gta02_jbt6k74_reset cannot be
resolved.
There are many ways to fix this - this one does it with a bit of a
swagger ;-)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix re-enabling of GPS on resume
The call to gps_pwron_set(0) during suspend would clear power_was_on
flag so the on/off status was always lost. Additionally when enabling/
disabling the regulator check its actual state, not power_was_on flag
(they don't match on resume).
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
This configuration (CONFIG_DISPLAY_L1K002) is GTA03 specific.
Let's disable it for GTA02.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
When in a kernel panic, we try to turn on the backlight. Because
of the panic, preempt is disabled at that time. Unfortunately,
operating the backlight requires access to I2C, and I2C likes to
sleep.
All this results in the kernel unleashing a nearly endless flood
of complaints complete with stack traces, etc., which often
obscures the real issue.
This patch is one way to improve the situation: it just skips
touching the backlight if we're in an atomic context. However, it
isn't perfect: it would be desirable if the backlight did get
turned on also on a panic. To do so, we would need to use I2C in
a way that doesn't sleep.
So I wonder if this is good enough or if someone has any plans to
make a better solution ?
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
-device-driv-1232448327
pending-tracking-hist top was MERGE-via-stable-tracking-add-tpo-l1k002-lcm-device-driv-1232448327 / 776c842e391a2fbc8e85cab38c90be2ce44e7cf7 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-add-tpo-l1k002-lcm-device-driv
stable-tracking-hist top was add-tpo-l1k002-lcm-device-driv / 738664a979e3fa43f3d53989390ce6212c818c92 ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
Add TPO L1K002 LCM device driver.
This device is adopted as LCM of gta03.
The patch provides the initialization for this LCM driver IC.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
pending-tracking-hist top was subject-usb-gadget-fix-rndis-w / 8a5ccc279cef316a16f921d7486f4a9efa234493 ... parent commitmessage:
From: David Brownell <dbrownell@users.sourceforge.net>
Subject: USB: gadget: fix rndis working at high speed
X-Git-Tag: v2.6.28-rc9~8^2~7
X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=7c12414955e9b44a3e33d54e578bf008caa4475d
USB: gadget: fix rndis working at high speed
Fix a bug specific to highspeed mode in the recently updated RNDIS
support: it wasn't setting up the high speed notification endpoint,
which prevented high speed RNDIS links from working.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Tested-by: Anand Gadiyar <gadiyar@ti.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
pending-tracking-hist top was subject-usb-gadget-rndis-send- / 3c29888770bfa8ce3a5e2ed590c3edb97ca4abaf ... parent commitmessage:
From: Richard Röjfors <richard.rojfors@endian.se>
Subject: USB: gadget rndis: send notifications
X-Git-Tag: v2.6.28-rc6~2^2~2
X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=ff3495052af48f7a2bf7961b131dc9e161dae19c;hp=9c264521a9f836541c122b00f505cfd60cc5bbb5
USB: gadget rndis: send notifications
It turns out that atomic_inc_return() returns the *new* value
not the original one, so the logic in rndis_response_available()
kept the first RNDIS response notification from getting out.
This prevented interoperation with MS-Windows (but not Linux).
Fix this to make RNDIS behave again.
Signed-off-by: Richard Röjfors <richard.rojfors@endian.se>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
lt-configura-1232397413
pending-tracking-hist top was MERGE-via-stable-tracking-update-gta02-default-configura-1232397413 / fdaef96a49003c3e907629757f489585ea6708ab ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-update-gta02-default-configura
stable-tracking-hist top was update-gta02-default-configura / ae4b4dc366b578f90cd85eda9348d3f7e585670c ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
update GTA02 default configurations
Add the settings introduced by the previous two patches to the default
configurations.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add the settings introduced by the previous two patches to the default
configurations.
(AG: this one is packaging config, the moredrivers one is on stable-tracking)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
screen-filte-1232327393
pending-tracking-hist top was MERGE-via-stable-tracking-fix-pcap7200-touchscreen-filte-1232327393 / 751df35b8e57667cc0669a7437f80b6c025f24ec ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-fix-pcap7200-touchscreen-filte
stable-tracking-hist top was fix-pcap7200-touchscreen-filte / e053b5719609ded159a22bcd1889bbd2611789ba ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-pcap7200-touchscreen-filter-move.patch
pcap7200 driver also uses our filter chain stuff now, so it needed a little
fixup when the includes moved for upstream
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This patch cleans up the GTA02 WLAN power control platform device:
- remove misleading /sys/devices/platform/gta02-pm-wlan.0/power_on
Users really wishing to play with reset can just gpio j12=0
- rename gta02_wlan_power to gta02_wlan_reset, because that's what it
truly is
- remove handling of GTA02_CHIP_PWD because
- it's not used, say our schematics
- even if it is, it's sampled long before we could affect it
- move SDIO-specific conversion from "power switch" to "reset
button" logic from gta02_wlan_reset to gta02_s3c_mmc_set_power
- removed mutex protection because we now only have a single user
A note in passing: we can probably do away with gta02_pm_wlan
completely once upstream rfkill adds better support for type-based
control.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Here's a bunch of changes to neo1973_pm_gps.c. The thing I set out to
change was just the initial power state, but there's so much wrong in
there, I couldn't resist slaying some evil on the way:
- update the copyright year
- show slightly more confidence in operator precedence
- simplify #ifdef rat's nest a little
- rename "pwron" sysfs file to "power_on", to conform to all the rest
- wrap lines longer than 80 columns
- use PTR_ERR, not cast
- reduce redundancy and increase readability in code patching
gta01_gps_sysfs_entries
- on GTA02 and if booted by u-boot, GPS is powered on. Power it off,
like on GTA01 or with Qi.
It's still nasty, but slightly less painful to look at now. Tested on
GTA02 and tested that it still compiles for GTA01.
The name change from "pwron" to "power_on" may be controversial. If
this causes undue misery for distribution makers, please holler.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Our suspend/resume debugging code in vprintk uses global_inside_suspend,
which is only defined if CONFIG_PM is enabled.
Fortunately, the fix is straightforward: if there's no CONFIG_PM, then
there's nothing to debug here either :-)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
global_inside_suspend only exists if CONFIG_PM is enabled.
We're actually the only ones using it outside power management,
so I guess it's okay not to try to find a more elegant solution
for upstream.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix suspend/resume dummy in mach-s3c2410/pwm.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix resume dummy in jbt6k74.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Fix suspend/resume dummy in glamo-fb.c
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
lter-include-1232325217
pending-tracking-hist top was MERGE-via-stable-tracking-fix-touchscreen-filter-include-1232325217 / d063e8c6d85c48de80b3d158bfa98d5a97149711 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-fix-touchscreen-filter-include
stable-tracking-hist top was fix-touchscreen-filter-include / bb151f28fc8e8923baad96e0f3e8f0ae57af95f5 ... parent commitmessage:
From: Nelson Castillo <arhuaco@freaks-unidos.net>
Fix touchscreen filter includes
Fix #includes to make the kernel compile again.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
-the-ar6000-1232104308
pending-tracking-hist top was MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308 / 09faeb511e9e6872c79b4d1ea2f3b5fefc16f3a1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-rfkill-support-for-the-ar6000-
stable-tracking-hist top was rfkill-support-for-the-ar6000- / e82f8ffa04ebcb05506c8e22268371c3c3b03173 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
rfkill support for the AR6000 driver
This patch adds rfkill support to the AR6000 driver. The driver does
not directly implement an rfkill device but uses the help of a special
platform device, such that the latter can retain rfkill state when the
AR6k driver is removed (e.g., because of suspend).
If an attempt is made to bring the driver up (module load, bind, or
resume) while rfkill is blocking, only the driver's data structures
are initialized, but function activation and most of the rest of the
setup is deferred until the rfkill block is removed.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
pending-tracking-hist top was clean-pcf50633-delete-deprecat / 4eb8d070641202940f12587b7efb77cac781b19d ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
clean-pcf50633-delete-deprecated-sensors-version.patch
Proposed-by: Sven sleipnir Rebhan <odinshorse@googlemail.com>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
When building the MMC subsystem as modules,
drivers/mfd/glamo/glamo-mci.ko cannot access irq_desc, because it
isn't exported by kernel/irq/handle.c All the functions that
indirectly access irq_desc are inlined, so they cannot be used to
avoid having to resolve irq_desc.
Fortunately, we can solve the problem locally: we don't really need
to access irq_desc anyway. This patch splits glamo_mci_irq into a
small wrapper that implements the IRQ handler interface and the main
code that doesn't need to know about the semantics of the latter.
Then we simply call the main code with the information we already
have.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Tested-by: Rafael Ignacio Zurita <rizurita@yahoo.com>
|
|
As I've mentioned before, telling the WLAN module not to sleep
with "wmiconfig -i eth0 --power maxperf" reportedly improves
network stability in some situations where otherwise disconnects
were frequent. (Sorry if this sounds rather vague. I don't have
much real data on this phenomenon. More details would be welcome.)
Paul Lever from Atheros suggested that one possible source of
trouble when not using --power maxperf could be that the module
very often takes a nap and then needs to delay new commands while
waking up, and some SDIO hosts may fail to handle the delay
properly.
The S3C2442 manual leaves it unclear whether the controller handles
this condition or not. The Linux MMC/SDIO stack explicitly polls
for busy status in MMC mode but not in SDIO mode.
I've attached a patch against andy-tracking that rather crudely
checks if the module is signalling that it's still busy while we're
about to start a new transfer, and delays in this case.
In my tests, I could not make the busy condition occur (unless I
explicitly violated the stack's synchronization), but then I hardly
see any disconnects anyway.
So it would be good if those affected by frequent loss of association
could try this patch. More precisely,
- if association with the base station is often lost, and
- "wmiconfig -i eth0 --power maxperf" improves this, then
- please apply this patch, leave WLAN power at default settings
(i.e., wmiconfig -i eth0 --power rec), and report
- if the patch had any effect on the stability of associations, and
- whether "READ WHILE BUSY !" or "WRITE WHILE BUSY !" gets
logged in dmesg.
It may make sense to temporarily put this patch into andy-tracking.
While it may be perfectly useless, it shouldn't create any new
trouble either. In case it turns out to make a difference, I'll have
to find a better place in the stack for it, so it'll be reverted
either way.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Michael Trimarchi <trimarchimichael@yahoo.it>
|
|
e-i2c-driver-1231835937
pending-tracking-hist top was MERGE-via-stable-tracking-add-id_table-in-the-i2c-driver-1231835937 / cf8dd84d83700bf038b2de4376ce238f09499a15 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-add-id_table-in-the-i2c-driver
stable-tracking-hist top was add-id_table-in-the-i2c-driver / 6c0bc11ccbb35c7477cc1208ab454ba5b6bf08b1 ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
Add id_table in the i2c driver struct of lp5521.
In new style i2c client, i2c driver should have id_table to match its device id.
Otherwise, the attachment of i2c driver would be failed.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
ko-kernel-bo-1231786968
pending-tracking-hist top was MERGE-via-stable-tracking-return-path-openmoko-kernel-bo-1231786968 / 74cc4a9339e8cc15f05d94f76f851313f7667bcd ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-return-path-openmoko-kernel-bo
stable-tracking-hist top was return-path-openmoko-kernel-bo / 05074908ceb3fd6cf9fdc218571c3bb1adc26cca ... parent commitmessage:
From: Andy Green <agreen@pads.home.warmcat.com>
Return-Path: <openmoko-kernel-bounces@lists.openmoko.org>
Received: from mail.openmoko.org ([unix socket])
by mail.openmoko.org (Cyrus v2.1.18-IPv6-Debian-2.1.18-5.1) with LMTP; Mon, 12 Jan 2009 17:42:13 +0000
X-Sieve: CMU Sieve 2.2
Return-path: <openmoko-kernel-bounces@lists.openmoko.org>
Received: from sita.openmoko.org ([88.198.124.203])
by mail.openmoko.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
(Exim 4.63)
(envelope-from <openmoko-kernel-bounces@lists.openmoko.org>)
id 1LMQnk-00023C-W3
for andy@imap.openmoko.org; Mon, 12 Jan 2009 17:42:13 +0000
Received: from localhost ([127.0.0.1] helo=sita.openmoko.org)
by sita.openmoko.org with esmtp (Exim 4.63)
(envelope-from <openmoko-kernel-bounces@lists.openmoko.org>)
id 1LMQnH-00021T-Ub; Mon, 12 Jan 2009 18:41:43 +0100
Received: from aakash.openmoko.org ([124.219.5.209])
by sita.openmoko.org with esmtp (Exim 4.63)
(envelope-from <matt_hsu@openmoko.org>)
id 1LMQnC-00021F-QB; Mon, 12 Jan 2009 18:41:42 +0100
Received: from [172.16.23.143] (helo=abacus-om.tw.openmoko.com
ident=Debian-exim)
by aakash.openmoko.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
(Exim 4.63) (envelope-from <matt_hsu@openmoko.org>)
id 1LMQhU-000398-Ik; Tue, 13 Jan 2009 01:35:54 +0800
Received: from matt by abacus-om.tw.openmoko.com with local (Exim 4.69)
(envelope-from <matt_hsu@openmoko.org>)
id 1LMRF1-0006Dl-2R; Tue, 13 Jan 2009 02:10:23 +0800
From: Matt Hsu <matt_hsu@openmoko.org>
To: openmoko-kernel@lists.openmoko.org
Date: Tue, 13 Jan 2009 02:10:23 +0800
Message-Id: <1231783823-23893-1-git-send-email-matt_hsu@openmoko.org>
X-Mailer: git-send-email 1.5.6.5
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on sita.openmoko.org
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham
version=3.2.3
Subject: [PATCH] This patch fixs compiling warnings of pcap7200_ts driver.
Cc: matt_hsu@openmoko.com
X-BeenThere: openmoko-kernel@lists.openmoko.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion regarding the OpenMoko Linux Kernel and boot loader
<openmoko-kernel.lists.openmoko.org>
List-Unsubscribe: <http://lists.openmoko.org/mailman/listinfo/openmoko-kernel>,
<mailto:openmoko-kernel-request@lists.openmoko.org?subject=unsubscribe>
List-Archive: <http://lists.openmoko.org/pipermail/openmoko-kernel>
List-Post: <mailto:openmoko-kernel@lists.openmoko.org>
List-Help: <mailto:openmoko-kernel-request@lists.openmoko.org?subject=help>
List-Subscribe: <http://lists.openmoko.org/mailman/listinfo/openmoko-kernel>,
<mailto:openmoko-kernel-request@lists.openmoko.org?subject=subscribe>
Sender: openmoko-kernel-bounces@lists.openmoko.org
Errors-To: openmoko-kernel-bounces@lists.openmoko.org
In addition, it adds handling in case of any failures after creating sysfs.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
This patch removes CONFIG_MD from gta02-moredrivers-defconfig, which
was dropped from the previous combined cleanup. It also removes
CONFIG_MMC_SDHCI from both GTA02 defconfigs, since this kind of
hardware doesn't exist in the S3C2442.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
00-guts-patc-1231750955
pending-tracking-hist top was MERGE-via-stable-tracking-add-missing-pcap7200-guts-patc-1231750955 / e65b1767efec44dadf4ee7163bedffc0aedfd06e ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-add-missing-pcap7200-guts-patc
stable-tracking-hist top was add-missing-pcap7200-guts-patc / c010223ac23687b8a5c129dd389328b844445cde ... parent commitmessage:
From: Matt Hsu <matt_hsu@openmoko.org>
add-missing-pcap7200-guts.patch
Patch by hand vs stg add issue...
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
This patch changes the two GTA02 default configurations[1] to build
the AR6k driver and S3C MCI (which is used exclusively by AR6k)
as modules. This way, WLAN can be brought up only if we actually
need it.
The patch also disables CONFIG_MD, which served no clear purpose.
[1] andy removed the moredrivers part despite asking for it
because it can be useful to have it built in without syncing
the rootfs, so the packaging config alone has it as modules.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
