linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev@vuser.vu.union.edu>,
	Ulrik De Bie <winmute@atlantique.venturi.net>
Subject: Re: vgacon, vga16fb, clgenfb on PPC
Date: Thu, 27 Jan 2000 15:12:22 -0700	[thread overview]
Message-ID: <20000127151222.W14218@hq.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10001272250560.428-100000@callisto.of.borg>; from Geert Uytterhoeven on Thu, Jan 27, 2000 at 11:00:32PM +0100


I lost all my PReP boxes and can't test anymore.  Motorola has a bunch of
guys on staff doing linux/ppc development for their systems (PReP) now so
you may want to have them test.

For now feel free to push it to the bk tree here.

} 	Hi,
}
} Finally I was able to compile a recent kernel again (2.3.41 from
} bitkeeper/PPC)!
}
} I revised my patch to make vga16fb and clgenfb compile (as modules, in my
} case). I couldn't test clgenfb, but vga16fb works fine as my second head (S3
} Trio64V+ initialized by em86, first head on ATI Rage II+ handled by atyfb).
}
} Compared to my previous version from 2 months ago, I think I found the bug that
} caused the endianness problems with vgacon on PReP: defining
} scr_memcpyw_{from,to} to be equal to memcpy() was wrong, since in that case no
} byteswapping was done when accessing video memory.
}
} The idea behind this patch is to make scr_{write,read}w() use {write,read}w()
} when {vga,mda}con is compiled in (independent of CONFIG_FB), and to use native
} byte ordering when it isn't.
}
} This patch is especially interesting for people who want to
}
}   - have a second head handled by vga16fb
}   - use clgenfb
}   - have vgacon on one head and clgenfb on the second
}   - ...

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-27 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-27 22:00 vgacon, vga16fb, clgenfb on PPC Geert Uytterhoeven
2000-01-27 22:12 ` Cort Dougan [this message]
2000-01-27 22:17 ` [linux-fbdev] " Jeff Garzik
2000-01-27 22:38   ` Geert Uytterhoeven
2000-01-27 22:30 ` Jeff Rugen
2000-01-27 22:39   ` Geert Uytterhoeven
2000-01-27 23:03     ` Cort Dougan

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=20000127151222.W14218@hq.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=winmute@atlantique.venturi.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).