Re: =?iso-8859-1?Q?=22make build=22?= died

Well, I've pretty much answered my own question. I'm still not quite sure 
why the build died -- though my suspicion is that I actually ran out of swap 
space (since, before I had swap space, I got signal 11 deaths on packages 
when I ran out of RAM). 

As far as the shell dying, though, it's definitely a case of compatibility 
between the kernel and the program. It appears that, in some cases, if the 
kernel is newer than the program -- for example, I had a kernel compiled 
from release sources, and bash from Josh's 1.6F tarball -- the program can't 
handle it, and will coredump. I've fixed this issue by switching my default 
shell to /bin/sh, which built and installed OK, and then rebuilding bash. 

If anyone has any insight as to why this would occur, it'd be sincerely 
appreciated. Meanwhile, I think I'm going to try using the build.sh script 
to rebuild world, and hopefully be successful this time. 

Alex Kirk

Re: "make build" died

--- Alex Kirk <alex <at> schnarff.com> wrote:
> As far as the shell dying, though, it's definitely a
> case of compatibility 
> between the kernel and the program. It appears that,
> in some cases, if the 
> kernel is newer than the program -- for example, I
> had a kernel compiled 
> from release sources, and bash from Josh's 1.6F
> tarball -- the program can't 
> handle it, and will coredump. I've fixed this issue
> by switching my default 
> shell to /bin/sh, which built and installed OK, and
> then rebuilding bash. 

Ah yeah. Me not being a -current buff, I think I led
you in the wrong direction last time. I was reading
about -current and they specifically warn you about
kernel incompatibilities. They don't try to lock down
binary compatibility in -current like they do in
-release. So you're on your own sometimes. This
happens to be one of those times it looks like.

(Still not able to build and burn my own kernel by the
way, sidetracked trying to netboot my Sparc1...)

Andy

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!

Re: =?iso-8859-1?Q?=22make build=22?= died

Alex Kirk <alex <at> schnarff.com> wrote:
>As far as the shell dying, though, it's definitely a case of compatibility 
>between the kernel and the program. It appears that, in some cases, if the 
>kernel is newer than the program -- for example, I had a kernel compiled 
>from release sources, and bash from Josh's 1.6F tarball -- the program can't 
>handle it, and will coredump.

Actually, I'm surprised that everything didn't core dump.

You were trying to run a -1-6 branch kernel with a -current (e.g.
syscall-wise newer than -1-6) userland.  That is a big no-no.

Please see http://www.netbsd.org/Releases/release-map.html for an
explanation of release numbering.  Basically, 1.6Letter is always
to be treated as "newer" than 1.6_{ALPHA,BETA,RC}*, 1.6, or 1.6.number.

jdarrow

--

-- 
John Darrow - Senior Technical Specialist               Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187  Fax:    630/752-5968
Pager via email: 6303160707 <at> alphapage.airtouch.com      Pager:  630/316-0707
Email: John.P.Darrow <at> wheaton.edu (plain text please, no HTML or proprietary)

(unknown)

Marcus, 

I'm sending this message to you primarily because you're the one with the 
technical knowledge to answer, and the list because it'll be good for 
archival purposes. 

When I first started working with NetBSD/Dreamcast, I asked about the video 
going off the edge of my TV screen; I believe you mentioned something about 
recompiling my kernel to fix it. Well, I looked at man options and wscons a 
bit, and figured that setting my display to 80x25 instead of 80x30 would do 
the trick; I tried compiling a new kernel with "options WSEMUL_80X25", and 
tried setting console 0 to 80x25 in /etc/wscons.conf. Neither seemed to 
work. 

Next, I figured I should take a look at the video driver, to see if there 
were any obvious variables I could tweak. Not being much more than a 
beginning C programmer, and knowing even less about how the OS files are 
laid out, I poked around until I found 
/usr/src/sys/arch/dreamcast/dev/pvr.c, which appeared to be the video driver 
(I was going from the line "pvr0 at shb0: 640 x 480, 16bpp, NTSC, composite" 
in dmesg). 

In there, I noticed a section commented as being for 60 Hz NTSC, and figured 
I was in the right place. I tried dropping the v_absolute_size variable by 
100 and recompiling my kernel; that caused my display to be unreadable. I 
set that back and tried dropping the vborder_stop variable by 50, and that 
didn't seem to do much, if anything. 

Am I even in the right neighborhood here? If not, what should I be doing? 
Any pointers would be greatly appreciated. 

maple driver

  Hello,

I'm now working on Maple (controller port) device drivers.
Any sort of comments and suggestions are welcome.
(Probably this needs more work.)

Some keywords are:
 - interrupt driven
 - support hot swapping
 - offer command interface to sub-drivers, not just periodic GETCOND

No function is added for now (but I'm working on memory card driver).
This patch also includes changes to sysasic driver.

Since the autoconfiguration framework is frequently changed recently,
the patch may not cleanly applied.

Regards,
--

-- 
ITOH Yasufumi

Index: conf/GENERIC
===================================================================
RCS file: /cvsroot/syssrc/sys/arch/dreamcast/conf/GENERIC,v
retrieving revision 1.26
diff -u -r1.26 GENERIC
--- conf/GENERIC	2002/09/18 02:43:57	1.26
+++ conf/GENERIC	2002/10/04 14:32:46
 <at>  <at>  -39,10 +39,10  <at>  <at> 

Re: none

"Alex Kirk" <alex <at> schnarff.com> writes:

> Marcus, I'm sending this message to you primarily because you're the
> one with the technical knowledge to answer, and the list because it'll
> be good for archival purposes. When I first started working with
> NetBSD/Dreamcast, I asked about the video going off the edge of my TV
> screen; I believe you mentioned something about recompiling my kernel
> to fix it. Well, I looked at man options and wscons a bit, and figured
> that setting my display to 80x25 instead of 80x30 would do the trick;
> I tried compiling a new kernel with "options WSEMUL_80X25", and tried
> setting console 0 to 80x25 in /etc/wscons.conf. Neither seemed to
> work. Next, I figured I should take a look at the video driver, to see
> if there were any obvious variables I could tweak. Not being much more
> than a beginning C programmer, and knowing even less about how the OS
> files are laid out, I poked around until I found
> /usr/src/sys/arch/dreamcast/dev/pvr.c, which appeared to be the video
> driver (I was going from the line "pvr0 at shb0: 640 x 480, 16bpp,
> NTSC, composite" in dmesg). In there, I noticed a section commented as
> being for 60 Hz NTSC, and figured I was in the right place. I tried
> dropping the v_absolute_size variable by 100 and recompiling my
> kernel; that caused my display to be unreadable. I set that back and
> tried dropping the vborder_stop variable by 50, and that didn't seem
> to do much, if anything. Am I even in the right neighborhood here? If
> not, what should I be doing? Any pointers would be greatly
> appreciated. Alex Kirk

Changing the border start/stop will not do much, since it only
controls where the _border_ is displayed (and it's black, so you won't
see it anyway).  If you want to move the actual picture, it's voffset

Re: maple driver

--- ITOH Yasufumi <itohy <at> netbsd.org> wrote:
> No function is added for now (but I'm working on
> memory card driver).

What uses would this have? It would be neat if you
could bootstrap a kernel stored on it, but other than
that, is there a lot of use for it other than just
making it work?

Thanks for the work. Seems like the Dreamcast is
getting more attention these days. Glad to see it.

Andy

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: maple driver

On Friday 04 Oct 2002 6:05 pm, Andy R wrote:
> --- ITOH Yasufumi <itohy <at> netbsd.org> wrote:
> > No function is added for now (but I'm working on
> > memory card driver).
>
> What uses would this have? It would be neat if you
> could bootstrap a kernel stored on it, but other than
> that, is there a lot of use for it other than just
> making it work?

Well, I wrote the Linux memory card driver and you are right there is no 
immediate functional use for it. But, tell me, why is anyone bothering to 
port *nix to the Dreamcast?

You won't be able to bootstrap a kernel from it - well not unless you loaded 
some other software that allowed you to do that - but there is little point 
to that.

It can/could be used as some simple (and small) persistent storage. I am 
working on the vmu file system for Linux right now, in fact.

>
> Thanks for the work. Seems like the Dreamcast is
> getting more attention these days. Glad to see it.
>
> Andy
>
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!

Re: maple driver

Heh...

*Picturing the BSD Daemon displayed on the VMU LCD* :)

Now, can someone get NetBSD running on the stand-alone VMUs? :)

Thanks,
Josh

On Fri, 4 Oct 2002, Drew P. Vogel wrote:

> An awesome use for the VMUs has nothing to do with storage. Couldn't we
> use them as status indicators?
>
> Regards,
> Drew Vogel
>
>
> On Fri, 4 Oct 2002, Adrian McMenamin wrote:
>
> >On Friday 04 Oct 2002 6:05 pm, Andy R wrote:
> >> --- ITOH Yasufumi <itohy <at> netbsd.org> wrote:
> >> > No function is added for now (but I'm working on
> >> > memory card driver).
> >>
> >> What uses would this have? It would be neat if you
> >> could bootstrap a kernel stored on it, but other than
> >> that, is there a lot of use for it other than just
> >> making it work?
> >

Re: maple driver

On Friday 04 Oct 2002 7:05 pm, Drew P. Vogel wrote:
> An awesome use for the VMUs has nothing to do with storage. Couldn't we
> use them as status indicators?
>
Strictly speaking, that is not a memory card issue. It could be done I am 
sure, though.

My linux driver is for the memory, not the screen.