*BSD News Article 85783


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!arclight.uoregon.edu!pith.uoregon.edu!newsfeed.orst.edu!newshub.tc.umn.edu!lynx.unm.edu!illusion.eece.unm.edu!ahvezda
From: ahvezda@illusion.eece.unm.edu (Ales Vaclav Hvezda)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: Look for info about porting NetBSD
Date: 24 Dec 1996 23:14:07 GMT
Organization: University of New Mexico, Albuquerque
Lines: 34
Message-ID: <59po3v$oqn@lynx.unm.edu>
NNTP-Posting-Host: illusion.eece.unm.edu
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:5032

Hi all,

	I'm in the process of evaluating whether or not I want to port
NetBSD to a new 68k ('40 actually) board or just go out on my own and
write something unique :-).  I've been hunting around the net looking at
the various NetBSD sites (include the mailing lists) and even looked at 
the 1.2 source tree.  Does anybody have any suggestions on any other
information that might be of use: such as cross compilation enviroments
from either an existing/running NetBSD system or a non-NetBSD system.

	I'm also curious as to what tools are used to build a NetBSD kernel. 
Here's an example of something that I found confusing, take for instance 
a random bit of code from arch/mvme68k/mvme68k/locore.s:

        movl    sp@(4), d7              | get boothowto
        movl    sp@(8), d6              | get bootaddr
        movl    sp@(12),d5              | get bootctrllun
        movl    sp@(16),d4              | get bootdevlun

This code uses Motorola's assem. syntax and I was under the assumption that
gas was used in the build.  I thought I understood that gas prefers
AT&T syntax.  So how does NetBSD build the .s files?  Am I missing something
really obvious?   For the most part whenever I'm doing cross development
to a 68k system I'm using a patched gcc (the Cygnus crossgcc patch); and
the gas that is built (from binutils) doesn't particularly care
for Motorola syntax assembly.  Thanks for your patience and any info!

								-Ales

--
   v   v
Ales Hvezda
ahvezda@eece.unm.edu
http://www.eece.unm.edu/staff/ahvezda -- PRR