From: Michal Simek <michal.simek@petalogix.com>
To: monstr@monstr.eu
Cc: linux-kernel@vger.kernel.org, john.williams@petalogix.com,
Peter Korsgaard <jacmet@sunsite.dk>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 57/57] microblaze_v7: Uartlite for Microblaze
Date: Tue, 24 Mar 2009 17:03:54 +0100 [thread overview]
Message-ID: <49C9046A.6060708@petalogix.com> (raw)
In-Reply-To: <57d096a05c22f5b3dd1070e9ecd6e8e05b22e9b3.1237407249.git.monstr@monstr.eu>
Hi all,
Here is the small part of code which enable uartlite and serial of code
driver for Microblaze cpu.
Peter: I got ack from you in past. I believe that I still have it. Could
I keep your ACK there?
Thanks,
Michal
> From: Michal Simek <monstr@monstr.eu>
>
>
> Signed-off-by: Michal Simek <monstr@monstr.eu>
> ---
> drivers/serial/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/serial/Kconfig b/drivers/serial/Kconfig
> index 7d7f576..131901b 100644
> --- a/drivers/serial/Kconfig
> +++ b/drivers/serial/Kconfig
> @@ -833,7 +833,7 @@ config SERIAL_IMX_CONSOLE
>
> config SERIAL_UARTLITE
> tristate "Xilinx uartlite serial port support"
> - depends on PPC32
> + depends on PPC32 || MICROBLAZE
> select SERIAL_CORE
> help
> Say Y here if you want to use the Xilinx uartlite serial controller.
> @@ -1319,7 +1319,7 @@ config SERIAL_NETX_CONSOLE
>
> config SERIAL_OF_PLATFORM
> tristate "Serial port on Open Firmware platform bus"
> - depends on PPC_OF
> + depends on PPC_OF || MICROBLAZE
> depends on SERIAL_8250 || SERIAL_OF_PLATFORM_NWPSERIAL
> help
> If you have a PowerPC based system that has serial ports
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
next parent reply other threads:[~2009-03-24 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1237408284-8674-1-git-send-email-monstr@monstr.eu>
[not found] ` <1e1dc8ccd5abc4e51272f52465c6b9e5f847f947.1237407249.git.monstr@monstr.eu>
[not found] ` <14c123f2bae10a8b5fb76cd059ba105c212776ef.1237407249.git.monstr@monstr.eu>
[not found] ` <4947b1131c14c1526b81493f461606018bd0f090.1237407249.git.monstr@monstr.eu>
[not found] ` <46bc9a74719cb3c21dfdd558b93bec8c5b5675d8.1237407249.git.monstr@monstr.eu>
[not found] ` <d3f49195b8f675db48d2eda4f09fddb51af6f946.1237407249.git.monstr@monstr.eu>
[not found] ` <34c2f9e50610e147be556607e482b88fd674b887.1237407249.git.monstr@monstr.eu>
[not found] ` <15f6f10873f7c6f4f3b06f9d4d5af3ee9714f873.1237407249.git.monstr@monstr.eu>
[not found] ` <e5b88f50c39aa95431f5ecdb032c6676399ae198.1237407249.git.monstr@monstr.eu>
[not found] ` <50253611a0770c1ae6a63702208cfb9f96cd1f1a.1237407249.git.monstr@monstr.eu>
[not found] ` <28a81149bf51571cbc898a672efff4770fbc1efe.1237407249.git.mons tr@monstr.eu>
[not found] ` <55868bc389e07d10d00e92a1da65f31256a26f4c.1237407249.git.monstr@monstr.eu>
[not found] ` <57d096a05c22f5b3dd1070e9ecd6e8e05b22e9b3.1237407249.git.monstr@monstr.eu>
2009-03-24 16:03 ` Michal Simek [this message]
2009-03-24 16:22 ` [PATCH 57/57] microblaze_v7: Uartlite for Microblaze John Williams
2009-03-24 16:47 ` Peter Korsgaard
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=49C9046A.6060708@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=jacmet@sunsite.dk \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=monstr@monstr.eu \
/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