public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hartmann <jhartmann@valinux.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Cavan <johnc@damncats.org>, linux-kernel@vger.kernel.org
Subject: Re: 4.1.0 DRM (was Re: Linux 2.4.6-ac3)
Date: Mon, 16 Jul 2001 12:00:23 -0600	[thread overview]
Message-ID: <3B532BB7.1050300@valinux.com> (raw)
In-Reply-To: <E15M6jC-0005PK-00@the-village.bc.nu>

Alan Cox wrote:

>> Why not do something similar to the aic7xxx driver? Place the old DRM in
>> code in a pre-X4.1.0 subdirectory, with a warning that it will become
>> obsolete as of 2.5, and bring in the new code. When you build the
>> kernel, you can then choose which DRM version you want and everybody is
>> happy.
> 
> 
> Thats certainly possible, Ideally you would want both module sets to 
> co-exist. That way the user can build all of DRM and get the right ones loading
> via modprobe
> 
> Alan
> 
> -
> 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/
> 

Actually I have something like this pretty much working.  Unfortunately 
I was working on a project full time during the 4.1.0 release.  With the 
addition of this code, the old modules will coexist with newer modules.  
Basically the newer modules will have their version numbers appended to 
their names, this way a user can build all the drm modules, and things 
will just work.  Hopefully we can get a 4.1.1 release out soon which 
will do this.  This will make the 4.0 -> 4.1 have to be a compile time 
decision, but 4.1 -> 4.1.1 and higher will just coexist with each 
other.  I'm currently working out integrating this into the kernel 
build, and I should hopefully have a patch for Linus and Alan soon.

-Jeff


  reply	other threads:[~2001-07-16 18:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 17:36 Linux 2.4.6-ac3 Alan Cox
2001-07-14 20:01 ` Zilvinas Valinskas
2001-07-14 20:05   ` Alan Cox
2001-07-15  1:45     ` Gareth Hughes
2001-07-15 13:12       ` Alan Cox
2001-07-15 14:01         ` Gareth Hughes
2001-07-15 15:31           ` Alan Cox
2001-07-16  1:29             ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Gareth Hughes
2001-07-16  1:51               ` Keith Owens
2001-07-16  2:07                 ` Gareth Hughes
2001-07-16 11:23               ` John Cavan
2001-07-16 11:39                 ` Alan Cox
2001-07-16 18:00                   ` Jeff Hartmann [this message]
2001-07-16 18:12                     ` Xavier Bestel
2001-07-16 18:32                       ` Jeff Hartmann
2001-07-16 18:42                     ` John Cavan
2001-07-16 19:32                       ` Jeff Hartmann
2001-07-16 19:34                         ` Xavier Bestel
2001-07-16 20:18                           ` Jeff Hartmann
2001-07-17  2:37                             ` Gareth Hughes
2001-07-17  8:31                           ` Mike A. Harris
2001-07-16 19:49                         ` John Cavan
2001-07-17  7:19                     ` 4.1.0 DRM Mike A. Harris
2001-07-17  5:28               ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Juan Quintela
2001-07-18  9:06                 ` Gareth Hughes
2001-07-18 16:21                   ` Juan Quintela
2001-07-18 13:30                 ` Mike A. Harris
2001-07-17 13:19             ` Linux 2.4.6-ac3 Zdenek Kabelac
2001-07-15  1:31 ` Linux 2.4.6-ac3 - some unresolved Eyal Lebedinsky
2001-07-15 13:09   ` Alan Cox

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=3B532BB7.1050300@valinux.com \
    --to=jhartmann@valinux.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=johnc@damncats.org \
    --cc=linux-kernel@vger.kernel.org \
    /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