From: Kumar Gala <galak@kernel.crashing.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Felipe Balbi <balbi@ti.com>
Subject: Re: defconfig for panda
Date: Fri, 30 Mar 2012 16:11:06 -0500 [thread overview]
Message-ID: <B05E7CFB-E2F3-426C-AAA8-622D715DB86A@kernel.crashing.org> (raw)
In-Reply-To: <20120330184859.GB8240@atomide.com>
On Mar 30, 2012, at 1:48 PM, Tony Lindgren wrote:
> Hi,
>
> * Kumar Gala <galak@kernel.crashing.org> [120329 12:24]:
>> As I'm new to the OMAP community this might be a stupid question but trying to just build and run a stock v3.3 kernel on a pandaboard. In doing so it seems as if some basic drivers are not enabled in omap2plus_defconfig for the board. I'm trying to figure out if this is normal for some reason or just an oversight.
>>
>> For example, USB and USB ethernet (SMC95xx). I notice the linaro kernel tree introduces an omap4_defconfig, so just wondering should I send patches to omap2plus_defconfig or what?
>
> We can add those to omap2plus_defconfig for sure, but let's have
> them added as modules. Then distros can use that easily in a
> standard way using initramfs-tools etc.
>
> Let's not change the drivers that are currently built in if they're
> needed for mounting mmc or nfsroot. Those can be changed later on.
I'll work up a patch, however I was doing this as I was trying to get NFS root working and thus would need USB + USB ethernet compiled in and not as modules for panda. Is that ok?
- k
next prev parent reply other threads:[~2012-03-30 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 19:21 defconfig for panda Kumar Gala
2012-03-30 18:48 ` Tony Lindgren
2012-03-30 21:11 ` Kumar Gala [this message]
2012-03-30 21:39 ` Tony Lindgren
2012-04-20 16:01 ` Matt Porter
2012-04-20 17:13 ` Tony Lindgren
2012-04-24 9:22 ` Raja, Govindraj
2012-05-08 22:04 ` Tony Lindgren
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=B05E7CFB-E2F3-426C-AAA8-622D715DB86A@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).