Re: DRM function pointer work..

From: Keith Whitwell (keith_at_tungstengraphics.com)
Date: 08/06/04

  • Next message: John Riggs: "PROBLEM: 2.6.7 Linux Kernel Crash While Detecting PCI Devices" 
    Date:	Fri, 06 Aug 2004 17:54:52 +0100
To: Ian Romanick <idr@us.ibm.com>

    Ian Romanick wrote:
    > Jon Smirl wrote:
    >
    >> The only case I see a problem is when drm-core is compiled into the
    >> kernel. Why don't we just change the Makefile to default to copying the
    >> CVS code into the kernel source tree and tell the user to rebuild his
    >> kernel?
    >
    >
    > I don't think that will fly with Joe-user that just wants to upgrade his
    > graphics driver. The other problem case is if the user has two graphics
    > cards in his system. He wants to upgrade the driver for one of them (or
    > install a new driver for a new card), but the interface between the
    > device-independent (in-kernel) layer and the device-dependent
    > (in-kernel) layer has changed.
    >
    > Unless there is some way to have multiple device-independent modules (on
    > a built-in and a module) loaded, the user is stuck in a situation where
    > he has to update both drivers, but it may not be obvious that they need
    > to do so.
    >
    > I don't think this situation is likely to happen, but if there is even
    > the potential for it to happen, we will get bitten. :(

    Yes, while I support the current rework and de-templatization of the code, I
    don't support any attempt to split the drm modules to try and share code at
    runtime - ie. I don't support a core/submodule approach.

    The arguments are pretty much the same as those against unbundling core mesa
    from the drivers - as soon as somebody tries to do an upgrade you're screwed.
      Anyone trying to run dual head with different 'versions' on each head,
    you're screwed.

    The last thing we need right now is a new ABI to worry about.

    Keith

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: John Riggs: "PROBLEM: 2.6.7 Linux Kernel Crash While Detecting PCI Devices"

    Relevant Pages

    • Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
      ... Use a HIGHMEM enabled kernel. ... Linux Plug and Play Support v0.97 Adam Belay ... Non-volatile memory driver v1.2 ... ehci_hcd 0000:00:13.2: new USB bus registered, ...
      (Linux-Kernel)
    • Re: 2.6.30-rc4 kernel
      ... I think there may be a problem with the 2.6.30 kernel that is ... # Generic Driver Options ... # PCI IDE chipsets support ... # Other IDE chipsets support ...
      (Linux-Kernel)
    • Re: 2.6.16-rc2-mm1: crash on suspend
      ... I've got a kernel crash when trying to suspend to disk. ... Mandriva Linux release 2006.1 for i586, ... # ACPI Support ... # Generic Driver Options ...
      (Linux-Kernel)
    • Re: Linux 2.6.13-rc4
      ... > ugly that I won't even show it (the kernel list would eat it as too big ... RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize ... ehci_hcd 0000:00:02.2: new USB bus registered, ... # ACPI Support ...
      (Linux-Kernel)
    • 2.6.30-rc4 kernel
      ... kernel panic - not syncing: ... # Generic Driver Options ... # PCI IDE chipsets support ... # Other IDE chipsets support ...
      (Linux-Kernel)