Re: [BK updates] fbdev changes updates.

On Tue, Oct 29, 2002 at 02:08:37PM -0800, James Simmons wrote:

quoted

On Tue, Oct 29, 2002 at 12:46:16PM -0800, James Simmons wrote:

quoted

OOps. Forgot the link.

bk://fbdev.bkbits.net/fbdev-2.5

Does it still contain the random file movearounds?

The reason I did this was to prevent adding another chuck of agp code. The
current work around for AGP fbdev drivers to have there OWN AGP code. So
we can leave the agp drivers where they are at or the framebuffer layer
can have its own AGP code for itself. Which way do you think it should be
done?

1) Fbdev layer has it own AGP layer

2) Use already existing AGP layer code.

Well, I'd be very happy if you could separate different things abit.
Everyone wants the console fixes in, but code placement is a bit more of a
policy issue and wants more discussion..  Even when they are in different
directories the drm drivers can always call into the fbdev drivers as "base
modules", like sis currently does.

quoted

quoted

On Tue, Oct 29, 2002 at 12:46:16PM -0800, James Simmons wrote:

quoted

OOps. Forgot the link.

bk://fbdev.bkbits.net/fbdev-2.5

Does it still contain the random file movearounds?

The reason I did this was to prevent adding another chuck of agp code. The
current work around for AGP fbdev drivers to have there OWN AGP code. So
we can leave the agp drivers where they are at or the framebuffer layer
can have its own AGP code for itself. Which way do you think it should be
done?

1) Fbdev layer has it own AGP layer

2) Use already existing AGP layer code.

Well, I'd be very happy if you could separate different things abit.
Everyone wants the console fixes in, but code placement is a bit more of a
policy issue and wants more discussion..  Even when they are in different
directories the drm drivers can always call into the fbdev drivers as "base
modules", like sis currently does.

Fair enough. I'm moving agp and dri back to drivers/char. I would
like to discuss a solution to how to initialize the AGP code quicker :-)