From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Proposed solution for interrupt mapping on CPCI and PPMC CPU ports
Date: Thu, 11 Oct 01 12:51:18 PDT [thread overview]
Message-ID: <0110111951.AA28062@ivan.Harhan.ORG> (raw)
Paul Mackerras <paulus@samba.org> wrote:
> Sounds OK, but I wonder why you want a binary format rather than
> something more easily human-readable?
Well, people can store this information wherever they want in whatever format
they want, but I would much prefer it being passed to the kernel in this simple
binary format rather than implement a parser for some human-oriented text
format in the board support files under arch/ppc/kernel.
--
Michael Sokolov 5791 VAN ALLEN WAY
Software Engineer CARLSBAD CA 92008-7321 USA
SBS Technologies, Inc. Phone: +1-760-438-6900 x2347
Communications Products or 1-888-SBS-COMM x2347
Fax: +1-760-438-6985
E-mail: msokolov@sbs.com
or msokolov@ivan.Harhan.ORG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-11 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 19:51 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 20:14 Proposed solution for interrupt mapping on CPCI and PPMC CPU ports Michael Sokolov
2001-10-11 0:12 ` Paul Mackerras
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=0110111951.AA28062@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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).