Hai,
On Wed, Jul 22, 2009 at 01:21:19PM +0200, Mark Kettenis wrote:
> > Talking of diffs, I think you forgot to attach in your last mail.
> Oops, here it is.
This hangs at the firmware version message also. Do you have a machine
you can test on? Perhaps it would be easier than sending diffs?
I'm
> Date: Wed, 22 Jul 2009 11:40:35 +0100
> From: Edd Barrett
>
> Talking of diffs, I think you forgot to attach in your last mail.
Oops, here it is.
Index: creator.c
===
RCS file: /cvs/src/sys/arch/sparc64/dev/creator.c,v
retrieving
On Wed, Jul 22, 2009 at 01:21:18AM +0200, Mark Kettenis wrote:
> Possibly because the console hasn't been set up propery yet at that
> point.
Oh no, it's because i turned off the console. X11 fights with getty,
causing the keyboard to be erratic in X11.
> > Also, on another note, does your sparc6
> Date: Tue, 21 Jul 2009 00:08:47 +0100
> From: Edd Barrett
>
> creator0: firmware rev 1.3.11
> panic: trap type 0x34 (mem address not aligned): pc=1344ff4 npc=1344ff8
> pstate=9
Oops, yes, I can see why that happens. New diff attached.
> How comes we don't get ddb on sparc64 btw?
Possibly be
On Mon, Jul 20, 2009 at 10:46:17PM +0200, Mark Kettenis wrote:
> Ugh, it seems that afbinit code does some sneaky word swapping.
> Here's a new diff.
>
>
> Index: creator.c
> ===
> RCS file: /cvs/src/sys/arch/sparc64/dev/creator.c,v
On Mon, Jul 20, 2009 at 10:46:17PM +0200, Mark Kettenis wrote:
> Ugh, it seems that afbinit code does some sneaky word swapping.
> Here's a new diff.
...
creator0: firmware rev 1.3.11
panic: trap type 0x34 (mem address not aligned): pc=1344ff4 npc=1344ff8
pstate=9
How comes we don't get ddb on sp
> Date: Mon, 20 Jul 2009 01:36:31 +0100
> From: Edd Barrett
>
> On Sun, Jul 19, 2009 at 10:36:47PM +0200, Mark Kettenis wrote:
> > Oops, I can see where that is going wrong. Here's a new diff.
>
> Now we get a freeze after the kernel reports the firmware version.
>
> Getting there :)
Ugh, it
On Sun, Jul 19, 2009 at 10:36:47PM +0200, Mark Kettenis wrote:
> Oops, I can see where that is going wrong. Here's a new diff.
Now we get a freeze after the kernel reports the firmware version.
Getting there :)
--
Best Regards
Edd Barrett
(Freelance software developer / technical writer / op
> Date: Sun, 19 Jul 2009 19:04:26 +0100
> From: Edd Barrett
>
> Hai,
>
> On Sun, Jul 19, 2009 at 04:25:20PM +0200, Mark Kettenis wrote:
> > Here is a diff that implements this. It expects to find the firmware
> > in the file /etc/firmware/afb to be more consistent with the firmwares
> > already
Hai,
On Sun, Jul 19, 2009 at 04:25:20PM +0200, Mark Kettenis wrote:
> Here is a diff that implements this. It expects to find the firmware
> in the file /etc/firmware/afb to be more consistent with the firmwares
> already there. Can you test this for me?
Oh n!
...
root on sd0a swap on sd0b
> Date: Sat, 18 Jul 2009 14:10:39 +0100
> From: Edd Barrett
>
> On Sat, Jul 18, 2009 at 10:43:49AM +0200, Mark Kettenis wrote:
> > int newmode, oldmode;
> >
> > ioctl(fd, WSDISPLAYIO_GMODE, &oldmode);
> > newmode = WSDISPLAYIO_MODE_MAPPED;
> > ioctl(fd, WSDISPLAYIO_SMODE, &ne
On Sat, Jul 18, 2009 at 10:43:49AM +0200, Mark Kettenis wrote:
> int newmode, oldmode;
>
> ioctl(fd, WSDISPLAYIO_GMODE, &oldmode);
> newmode = WSDISPLAYIO_MODE_MAPPED;
> ioctl(fd, WSDISPLAYIO_SMODE, &newmode);
>
> ...
>
> ioctl(fd, WSSDISPLAYIO_SMODE, &oldmode);
>
> Date: Sat, 18 Jul 2009 04:40:47 +0100
> From: Edd Barrett
>
> Hi Guys,
>
> I have managed to accelerate an Elite3D card on a Blade 1000. It
> requires a binary blob in order to work, the utility to do so is called
> afbinit and the port can be found here:
>
> http://students.dec.bmth.ac.uk/eb
Hi Guys,
I have managed to accelerate an Elite3D card on a Blade 1000. It
requires a binary blob in order to work, the utility to do so is called
afbinit and the port can be found here:
http://students.dec.bmth.ac.uk/ebarrett/files/afbinit.tgz
It works well once you get the firware on the card.
14 matches
Mail list logo
