From: Dan Malek <dan@embeddededge.com>
To: Steffen Rumler <Steffen.Rumler@siemens.com>
Cc: linuxppc <linuxppc-embedded@ozlabs.org>
Subject: Re: uart.c: avoid changing parameter RAM on-the-fly for the console
Date: Thu, 3 Feb 2005 10:43:55 -0500 [thread overview]
Message-ID: <754ecc31c2497b32a0c3f6df5ce21881@embeddededge.com> (raw)
In-Reply-To: <4202408A.7050200@siemens.com>
On Feb 3, 2005, at 10:17 AM, Steffen Rumler wrote:
> According to Motorola this is _NOT_ allowed and dangerous.
:-) yeah, ok ...
> I suggest to do this inside rs_8xx_init() and startup() as shown
> in the patch below.
would you please read Documentation/CodingStyle and
try sending the patch again?
Although it doesn't make too much difference in this case,
2.4.20 is pretty old and it helps to get patches against
the latest kernels.
> With this fix, the modules hanging before can boot now.
I suspect there is something else amiss, but I'll take a
look at it. What is the speed of the processor and the
baud rate?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-02-03 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 15:17 uart.c: avoid changing parameter RAM on-the-fly for the console Steffen Rumler
2005-02-03 15:43 ` Dan Malek [this message]
2005-02-04 8:55 ` Steffen Rumler
2005-02-16 9:56 ` Steffen Rumler
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=754ecc31c2497b32a0c3f6df5ce21881@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Steffen.Rumler@siemens.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).