From: Dirk Behme <dirk.behme@googlemail.com>
To: "Syed Mohammed, Khasim" <khasim@ti.com>
Cc: linux-omap@vger.kernel.org, discussion@beagleboard.org,
Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: [PATCH 3/4] Adding support for OMAP3 Beagle Board
Date: Thu, 17 Apr 2008 17:00:04 +0200 [thread overview]
Message-ID: <480765F4.6090001@googlemail.com> (raw)
In-Reply-To: <7EAD1AEEA7621C45899FE99123E124A0018C8CCF@dbde01.ent.ti.com>
Syed Mohammed, Khasim wrote:
> Hi Dirk,
>
>
>>>+}
>>>+
>>>+static struct omap_board_config_kernel omap3_beagle_config[] __initdata
>>
>>= {
>>
>>>+ {OMAP_TAG_UART, &omap3_beagle_uart_config },
>>>+};
>>>+
>>>+static void __init omap3_beagle_init(void)
>>>+{
>>>+ omap_board_config = omap3_beagle_config;
>>>+ omap_board_config_size = ARRAY_SIZE(omap3_beagle_config);
>>>+ omap_serial_init();
>>
>>Do you like to add here MMC and USB init like recently proposed by
>>Koen Kooi?
>>
>
> They are any ways adding new functionality we can bring them in as new patches. Just trying to avoid another round of testing :)
Yes, okay, with below hint this makes sense.
>>If I understand correctly, these patches currently won't boot on
>>BeagleBoard if MMC and USB are missing?
>>
>
> I have tried with Ramdisk. Kernel boots on Beagle with out USB and MMC.
Ah, maybe I missed this hint. Yes, with ramdisk it will work. I think
Koen's issue yesterday was to mount MMC card and this confused me ;)
Thanks for clarification,
Dirk
next prev parent reply other threads:[~2008-04-17 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 2:11 [PATCH 3/4] Adding support for OMAP3 Beagle Board Syed Mohammed, Khasim
2008-04-17 11:39 ` Felipe Balbi
2008-04-18 19:05 ` Tony Lindgren
2008-04-19 12:51 ` Felipe Balbi
2008-04-19 15:54 ` Syed Mohammed, Khasim
2008-04-19 20:14 ` Felipe Balbi
2008-04-21 18:04 ` Tony Lindgren
2008-04-17 14:32 ` Dirk Behme
2008-04-17 14:43 ` Syed Mohammed, Khasim
2008-04-17 15:00 ` Dirk Behme [this message]
2008-04-18 19:08 ` 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=480765F4.6090001@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=discussion@beagleboard.org \
--cc=k.kooi@student.utwente.nl \
--cc=khasim@ti.com \
--cc=linux-omap@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