From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: linuxppc-dev@ozlabs.org
Cc: Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCHv2 2/3] ep8248e: Reference SMC parameter RAM base in the device tree.
Date: Fri, 28 Mar 2008 15:06:58 +0100 [thread overview]
Message-ID: <200803281506.58988.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <200803281458.56766.laurentp@cse-semaphore.com>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On Friday 28 March 2008 14:58, Laurent Pinchart wrote:
> On Thursday 27 March 2008 16:39, Scott Wood wrote:
> > On Thu, Mar 27, 2008 at 10:10:33AM +0100, Laurent Pinchart wrote:
> > > On Wednesday 26 March 2008 17:59, Scott Wood wrote:
> > > > This breaks the bootwrapper console.
> > >
> > > And of course I forgot about that :-)
> > >
> > > The boot wrapper code doesn't have any dpram allocator. Any objection
against
> > > using a chunk of dpram at a fixed location ? What about at the beginning
of
> > > the dpram ? The DTS muram node would then exclude a chunk of dpram at
offset
> > > 0x0000 instead of 0x1100.
> >
> > I'm not entirely comfortable with using a chunk outside of what's in the
> > muram node, and assuming that it's for the SMC pram -- what if there's
> > microcode or something there?
> >
> > Since udbg is only for debugging, and is marked as potentially dangerous,
> > how about just using the end of muram (as described in the device tree)?
> > If the muram is fully allocated, it won't happen until after the real
> > serial console is initialized.
>
> Very good idea. I'll prepare a new patch.
arch/powerpc/boot/cpm-serial.c stores the udbg buffer descriptors at the
beginning of the muram. Should I move them at the end as well ?
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-28 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 11:17 [PATCHv2 0/3] cpm2: Reset the CPM at startup and fix the cpm_uart driver accordingly Laurent Pinchart
2008-03-26 11:19 ` [PATCHv2 1/3] cpm_uart: Allocate DPRAM memory for SMC ports on CPM2-based platforms Laurent Pinchart
2008-03-26 11:20 ` [PATCHv2 2/3] ep8248e: Reference SMC parameter RAM base in the device tree Laurent Pinchart
2008-03-26 15:57 ` Scott Wood
2008-03-27 9:07 ` Laurent Pinchart
2008-03-26 16:59 ` Scott Wood
2008-03-27 9:10 ` Laurent Pinchart
2008-03-27 15:39 ` Scott Wood
2008-03-28 13:58 ` Laurent Pinchart
2008-03-28 14:06 ` Laurent Pinchart [this message]
2008-03-28 15:22 ` Scott Wood
2008-03-28 16:26 ` Laurent Pinchart
2008-03-28 17:11 ` Scott Wood
2008-03-28 17:54 ` Laurent Pinchart
2008-03-28 18:07 ` Scott Wood
2008-03-31 9:08 ` Laurent Pinchart
2008-03-31 15:33 ` Scott Wood
2008-03-31 17:38 ` [PATCHv2 2/3] ep8248e: Reference SMC parameter RAM base in thedevice tree Rune Torgersen
2008-03-31 17:42 ` Scott Wood
2008-03-31 17:45 ` Rune Torgersen
2008-03-26 11:21 ` [PATCHv2 0/3] cpm2: Reset the CPM when early debugging is not enabled Laurent Pinchart
2008-03-26 11:22 ` Laurent Pinchart
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=200803281506.58988.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).