From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] microblaze: Enable SERIAL_MULTI
Date: Mon, 10 Oct 2011 12:52:20 +0200 [thread overview]
Message-ID: <4E92CE64.5000609@monstr.eu> (raw)
In-Reply-To: <CALButCJ2d9Us0RJcwxFyscjCZ+MkSv-jHaQwTNW1QySiVA-sXQ@mail.gmail.com>
Graeme Russ wrote:
> On 10/10/11, Michal Simek <monstr@monstr.eu> wrote:
>> Enable support for SERIAL_MULTI.
>>
>> Microblaze can use uart16550 and uartlite drivers.
>>
>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>>
>> ---
>> Note:
>> Follow serial.h conding style.
>> ---
>> arch/microblaze/lib/board.c | 4 ++++
>> include/configs/microblaze-generic.h | 2 ++
>> include/serial.h | 2 +-
>> 3 files changed, 7 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/microblaze/lib/board.c b/arch/microblaze/lib/board.c
>> index ca5882d..64089c8 100644
>> --- a/arch/microblaze/lib/board.c
>> +++ b/arch/microblaze/lib/board.c
>> @@ -32,6 +32,7 @@
>> #include <stdio_dev.h>
>> #include <net.h>
>> #include <asm/processor.h>
>> +#include <serial.h>
>>
>> DECLARE_GLOBAL_DATA_PTR;
>>
>> @@ -110,6 +111,9 @@ void board_init (void)
>>
>> monitor_flash_len = __end - __text_start;
>>
>> +#ifdef CONFIG_SERIAL_MULTI
>> + serial_initialize();
>> +#endif
>> /*
>> * The Malloc area is immediately below the monitor copy in DRAM
>> * aka CONFIG_SYS_MONITOR_BASE - Note there is no need for reloc_off
>> diff --git a/include/configs/microblaze-generic.h
>> b/include/configs/microblaze-generic.h
>> index 6b3fd76..89657189 100644
>> --- a/include/configs/microblaze-generic.h
>> +++ b/include/configs/microblaze-generic.h
>> @@ -31,6 +31,8 @@
>> #define CONFIG_MICROBLAZE 1
>> #define MICROBLAZE_V5 1
>>
>> +#define CONFIG_SERIAL_MULTI 1
>> +
>> /* uart */
>> #ifdef XILINX_UARTLITE_BASEADDR
>> # define CONFIG_XILINX_UARTLITE
>> diff --git a/include/serial.h b/include/serial.h
>> index 5926244..f047d2f 100644
>> --- a/include/serial.h
>> +++ b/include/serial.h
>> @@ -31,7 +31,7 @@ extern struct serial_device * default_serial_console
>> (void);
>> defined(CONFIG_MB86R0x) || defined(CONFIG_MPC5xxx) || \
>> defined(CONFIG_MPC83xx) || defined(CONFIG_MPC85xx) || \
>> defined(CONFIG_MPC86xx) || defined(CONFIG_SYS_SC520) || \
>> - defined(CONFIG_TEGRA2)
>> + defined(CONFIG_TEGRA2) || defined(CONFIG_MICROBLAZE)
>
> Am I the only one that thinks this is all really ugly?
I hope you mean serial.h not mb code.
I agree with you but not sure if we can remove all ifdefs there.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-10-10 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 7:17 [U-Boot] microblaze - serial multi Michal Simek
2011-10-10 7:17 ` [U-Boot] [PATCH] microblaze: Enable SERIAL_MULTI Michal Simek
2011-10-10 10:11 ` Graeme Russ
2011-10-10 10:52 ` Michal Simek [this message]
2011-10-10 12:57 ` Wolfgang Denk
2011-10-10 15:18 ` Mike Frysinger
2011-10-10 17:35 ` Wolfgang Denk
2011-10-10 17:52 ` Mike Frysinger
2011-10-10 18:26 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2011-09-06 14:22 [U-Boot] [PATCH v2] serial: uartlite: Support for SERIAL_MULTI Michal Simek
2011-09-06 14:22 ` [U-Boot] [PATCH] microblaze: Enable SERIAL_MULTI Michal Simek
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=4E92CE64.5000609@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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