From: "S. Egbert" <s.egbert@sbcglobal.net>
To: linuxppc-embedded@ozlabs.org
Subject: [PATCH 00/10] Updated ML300 & ML403 patches
Date: Wed, 08 Feb 2006 23:57:32 -0800 [thread overview]
Message-ID: <43EAF5EC.7050204@sbcglobal.net> (raw)
> > Really, this isn't statically defined anyway. The bootloader
> > (u-boot or zImage) passes the memory size into the kernel; and in
> > fact the kernel command line; or the board setup code can restrict
> > the amount of mem used by the kernel. XPAR_MEM_* isn't used by the
> > kernel proper at all.
> >
> > - Peter
>
> Thanks for the comments.
>
> Another issue we need to discuss is if/how to support the xilinx
> generated BSP in the kernel proper; but I'll leave that for a
> different email.
>
> If there's enough interest; I'll setup another git tree for the virtex
> specific patches.
I, for one, am interested in helping with the Virtex specific patches.
Is there a URL for this? git://?
S. Egbert
next reply other threads:[~2006-02-09 7:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 7:57 S. Egbert [this message]
2006-02-09 14:51 ` [PATCH 00/10] Updated ML300 & ML403 patches Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2006-01-27 12:01 Paula Saameño
2006-01-27 16:37 ` Grant Likely
[not found] <mailman.134.1137523561.17753.linuxppc-embedded@ozlabs.org>
2006-01-17 20:12 ` T Ziomek
2006-01-17 20:19 ` Grant Likely
2006-01-17 20:23 ` T Ziomek
2006-01-17 20:37 ` Grant Likely
2006-01-17 18:10 John Bonesio
2006-01-17 18:31 ` Grant Likely
2006-01-14 9:46 Grant Likely
[not found] ` <43CC5453.3060702@xilinx.com>
2006-01-17 7:39 ` Grant Likely
2006-01-17 12:52 ` Peter Ryser
2006-01-17 15:41 ` Grant Likely
2006-01-17 17:06 ` Peter Ryser
2006-01-17 17:30 ` Grant Likely
2006-01-17 19:31 ` Grant Likely
2006-01-18 23:26 ` Peter Ryser
2006-01-19 5:11 ` Grant Likely
2006-01-19 0:27 ` David H. Lynch Jr.
2006-01-19 7:14 ` jeffer
2006-01-19 7:29 ` Peter Ryser
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=43EAF5EC.7050204@sbcglobal.net \
--to=s.egbert@sbcglobal.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.