> Here is a third version that just integrates the coreboot code into
> efifb. The cnattach path still has to be different to allow vga to
> try to attach before doing the coreboot version.
>
>
> Index: arch/amd64/amd64/efifb.c
> @@ -55,6 +102,8 @@ int efifb_show_screen(void *, void *, i
On Mon, 13 Jun 2016 at 12:35:23 +0200, Mark Kettenis wrote:
> > Date: Sun, 12 Jun 2016 11:47:37 -0500
> > From: joshua stein
> >
> > Here's a new version with feedback from Miod and Ted.
> >
> > It also fixes a bug on a Broadwell Chromebook (tested by Edward
> > Wandasiewicz) which has proper in
> On Wed, 15 Jun 2016 19:01:23 +0200, Mark Kettenis wrote:
>
>> I don't really consider it to be terribly important to rename the
>> efifb(4). The chromebooks are weird machines, and I don't expect the
>> coreboot-based framebuffer to show up on many systems.
>
> Agreed, just keep it as efifb(4).
On Wed, 15 Jun 2016 19:01:23 +0200, Mark Kettenis wrote:
> I don't really consider it to be terribly important to rename the
> efifb(4). The chromebooks are weird machines, and I don't expect the
> coreboot-based framebuffer to show up on many systems.
Agreed, just keep it as efifb(4). If we re
> From: Bryan Vyhmeister
> Date: Wed, 15 Jun 2016 09:54:08 -0700
>
> On Wed, Jun 15, 2016, at 09:34 AM, Bryan Steele wrote:
> > On Wed, Jun 15, 2016 at 12:32:00PM -0400, Bryan Steele wrote:
> > > On Wed, Jun 15, 2016 at 11:23:53AM -0500, joshua stein wrote:
> > > > Any ideas for a new name?
> > >
On Wed, Jun 15, 2016, at 09:34 AM, Bryan Steele wrote:
> On Wed, Jun 15, 2016 at 12:32:00PM -0400, Bryan Steele wrote:
> > On Wed, Jun 15, 2016 at 11:23:53AM -0500, joshua stein wrote:
> > > Any ideas for a new name?
> >
> > NetBSD calls their equivalent driver genfb(4).
>
> I wonder if it could be
On Wed, Jun 15, 2016 at 12:32:00PM -0400, Bryan Steele wrote:
> On Wed, Jun 15, 2016 at 11:23:53AM -0500, joshua stein wrote:
> > On Tue, 14 Jun 2016 at 07:22:14 +0200, Joerg Jung wrote:
> > > > We should not get hung up too much about the driver name. If it is
> > > > felt that efifb(4) is inappr
On Wed, Jun 15, 2016 at 11:23:53AM -0500, joshua stein wrote:
> On Tue, 14 Jun 2016 at 07:22:14 +0200, Joerg Jung wrote:
> > > We should not get hung up too much about the driver name. If it is
> > > felt that efifb(4) is inappropriate for these chromebooks with
> > > coreboot, we can always renam
On Tue, 14 Jun 2016 at 07:22:14 +0200, Joerg Jung wrote:
> > We should not get hung up too much about the driver name. If it is
> > felt that efifb(4) is inappropriate for these chromebooks with
> > coreboot, we can always rename the driver.
>
> Yes, renaming makes sense then.
Any ideas for a ne
Am 13.06.2016 um 12:35 schrieb Mark Kettenis :
>> Date: Sun, 12 Jun 2016 11:47:37 -0500
>> From: joshua stein
>>
>> Here's a new version with feedback from Miod and Ted.
>>
>> It also fixes a bug on a Broadwell Chromebook (tested by Edward
>> Wandasiewicz) which has proper inteldrm but no vga,
> Date: Sun, 12 Jun 2016 11:47:37 -0500
> From: joshua stein
>
> Here's a new version with feedback from Miod and Ted.
>
> It also fixes a bug on a Broadwell Chromebook (tested by Edward
> Wandasiewicz) which has proper inteldrm but no vga, so cbfb was
> getting chosen as the console early on bu
Here's a new version with feedback from Miod and Ted.
It also fixes a bug on a Broadwell Chromebook (tested by Edward
Wandasiewicz) which has proper inteldrm but no vga, so cbfb was
getting chosen as the console early on but then not detaching when
inteldrm wanted to take over. This detaches cbfb
> Index: arch/amd64/amd64/cbfb.c
> +struct cfattach cbfb_ca = {
> + sizeof(struct cbfb_softc), cbfb_match, cbfb_attach, NULL
> +};
Make it const.
> +void
> +cbfb_rasops_preinit(struct cbfb *cbfb)
> +{
> +#define bmnum(_x) (fls(_x) - ffs(_x) + 1)
> +#define bmpos(_x) (ffs(_x) - 1)
These two
joshua stein wrote:
> +int
> +cb_parse_table(paddr_t addr)
> +{
> + int i, j;
> +
> + for (i = 0; i < (4 * 1024); i += 16) {
> + struct cb_header *cbh;
> + struct cb_entry *cbe;
> + void *cbtable;
> +
> + cbh = (struct cb_header *)(PMAP_DIRECT
> Date: Fri, 10 Jun 2016 14:38:05 -0500
> From: joshua stein
>
> This implements a new framebuffer console (based on efifb) for amd64
> devices running Coreboot, which do not have otherwise working EFI,
> VGA text, inteldrm, or serial console. So mostly just Skylake
> Chromebooks.
>
> This is r
This implements a new framebuffer console (based on efifb) for amd64
devices running Coreboot, which do not have otherwise working EFI,
VGA text, inteldrm, or serial console. So mostly just Skylake
Chromebooks.
This is required for my HP Chromebook 13 (and would have previously
been required for
16 matches
Mail list logo
