All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Whitehead <parman@bwhitehead.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: parman@bwhitehead.com
Subject: help with bootup code
Date: Wed, 28 Apr 1999 23:37:35 -0500	[thread overview]
Message-ID: <3727E20F.BC03ADD2@bwhitehead.com> (raw)


I am just learning Linux and hope to port it to a custom platform using
older I/O chipsets(W83c553 and 87307). Basically the system consists of
a 603/MPC106 with 64M sdram, PCI to ISA and IDE interface(W83c553), and
I/O controller(87307). I believe the basic system is already supportted
by Linux but support for I/O chipsets must be added. I am using LinuxPPC
4.1 while waiting for release 5.

I can load the compiled kernel into high memory and jump to head.S.

I have traced the boot code(arch/ppc/boot) and think I understand the
relocate, vga_init, and decompress code but am unable to determine where
the input is coming from when fill_inbuf() is called. It gets input from
an array(input_data[]?) but I can't find where the data is assigned to
that array. I don't see an open call, a pointer assignment, or a memcpy
to draw data from. The kernel isn't running yet so Linux device drivers
aren't supplying the data.

The code is something like "if ( data_ptr < buffer_size) {
data_inbuf[data_ptr] = input_data[offset]; data_ptr++;}". I am sorry but
I don't have the code accessible at the moment. If this is too confusing
to answer, I will re-submit it tomorrow evening when the source code
listings will be available. I check the list in the evening and am
trying to get feedback as soon as possible.

I have been monitoring this list for a few weeks and have not seen these
chips mentioned except once when someone, from Korea(?), indicated they
were interested in porting Linux to a Motorola YellowKnife system which
uses them. (if your that person let me know how its going!)

Thanks in advance for you help,

Bill Whitehead
parman@bwhitehead.com


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

             reply	other threads:[~1999-04-29  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-29  4:37 Bill Whitehead [this message]
1999-04-29 15:25 ` help with bootup code Geert Uytterhoeven
1999-04-29 17:03 ` Gary Thomas

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=3727E20F.BC03ADD2@bwhitehead.com \
    --to=parman@bwhitehead.com \
    --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 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.