All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Gray <dgray@ucsc.edu>
To: Blue Swirl <blueswir1@hotmail.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Accessing the serial port from proll
Date: Sun, 20 Nov 2005 02:11:31 -0800	[thread overview]
Message-ID: <43804BD3.90500@ucsc.edu> (raw)
In-Reply-To: <BAY104-F174897EB58B0D3F393D309FF500@phx.gbl>

Hi,

Thanks for the help.  I've actually tried using the function you 
suggest, but gotten the following error:

sparc-elf-gcc -O1 -W -Wall -DPROLBASE=0xffd00000 -DPROLDATA=0xffd0b000 
-DPROLRODATA=0xffd08000 -D__ANSI__=1 -I../src -mcpu=hypersparc 
-Wa,-xarch=v8 -g -DQEMU -m32 -fno-builtin -c main.c
sparc-elf-ld -N -Ttext 0xffd00000 --section-start .rodata=0xffd08000 
-Tdata 0xffd0b000 -Tbss 0xffd0b000 -o proll.elf head.o wuf.o wof.o 
main.o  printf.o le.o system_qemu.o iommu.o arp.o netinit.o bootp.o 
packet.o tftp.o udp.o sched_4m.o openprom.o vconsole.o hconsole.o 
rconsole.o vcons_zs.o esp.o
sparc-elf-ld: section .rodata [00000000ffd08000 -> 00000000ffd0a129] 
overlaps section .text [00000000ffd00000 -> 00000000ffd08077]
sparc-elf-ld: proll.elf: section .rodata lma 0xffd08000 overlaps 
previous sections
make: *** [proll.elf] Error 1

However when I tried your code snippet it works fine.  It seems that it 
only works if I call that function from an infinite loop (big loop or 
loops with a break statement don't compile either), which is driving me 
nuts.  Do you know why this is?

Also, some additional background info.  I am actually using the 
-nographic option.  This project is for a grad class on computer 
architecture.  The prof. says he has a sparc processor implemented on an 
fpga and wants to load linux on it, but it doesn't have a hard drive or 
network connection, so that is why I'm writing a serial loader.

-Doug

  reply	other threads:[~2005-11-20 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  9:25 [Qemu-devel] Re: Accessing the serial port from proll Blue Swirl
2005-11-20 10:11 ` Doug Gray [this message]
2005-11-20 12:50   ` Blue Swirl

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=43804BD3.90500@ucsc.edu \
    --to=dgray@ucsc.edu \
    --cc=blueswir1@hotmail.com \
    --cc=qemu-devel@nongnu.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.