Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
On Tue, 2005-01-04 at 22:28 +, Sergio Monteiro Basto wrote: > On Tue, 2005-01-04 at 22:07 +, Dave Airlie wrote: > > > > > > After think a little and put dri working with kernel 2.4. > > > The only solution, that I see, to not private users of savage with > > > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > > > before 2005-01-01 and other for kernel 2.6 > > > > Not really a good idea, the old code was not releaseable or secure, 2.4 is > > a fixes only tree, why do people want new drivers for it? if you are > > running production machines on it you won't want a dodgy DRM driver on > > it... > > > > you can always use CVS to checkout the old code... > > > > Dave. > > Ok I accept that, about releaseable and dodgy DRM drive, I agree. > > but just a tough, about security, nowadays it common say, errors are > security problems, I don't see how could drm be insecure. > DRM can be insecure because some hardware supports things like blitting any chunk of system memory from anywhere to anywhere. So you can't just let apps do anything, you have to verify the command stream somehow. Lee --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
> > Ok I accept that, about releaseable and dodgy DRM drive, I agree. > > but just a tough, about security, nowadays it common say, errors are > security problems, I don't see how could drm be insecure. Well if you have a multi-user machine, and they have access to the insecure drm, they can write some code to get the graphics card to DMA some root only RAM somewhere else, so things like passwd file contents etc can be gotten at ... it requires some knowledge of the graphics card but it is not beyond a decent hacker... (average script kiddie might have some issues...) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
On Tue, 2005-01-04 at 22:07 +, Dave Airlie wrote: > > > > After think a little and put dri working with kernel 2.4. > > The only solution, that I see, to not private users of savage with > > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > > before 2005-01-01 and other for kernel 2.6 > > Not really a good idea, the old code was not releaseable or secure, 2.4 is > a fixes only tree, why do people want new drivers for it? if you are > running production machines on it you won't want a dodgy DRM driver on > it... > > you can always use CVS to checkout the old code... > > Dave. Ok I accept that, about releaseable and dodgy DRM drive, I agree. but just a tough, about security, nowadays it common say, errors are security problems, I don't see how could drm be insecure. -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
> > After think a little and put dri working with kernel 2.4. > The only solution, that I see, to not private users of savage with > kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code > before 2005-01-01 and other for kernel 2.6 Not really a good idea, the old code was not releaseable or secure, 2.4 is a fixes only tree, why do people want new drivers for it? if you are running production machines on it you won't want a dodgy DRM driver on it... you can always use CVS to checkout the old code... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-users] Re: problems compiling xorg cvs Re: drm CVS state...
redirecting to devel ML On Mon, 2005-01-03 at 23:38 +, Sergio Monteiro Basto wrote: > If you're still using Linux 2.4 you need to upgrade that first. After think a little and put dri working with kernel 2.4. The only solution, that I see, to not private users of savage with kernel 2.4, have dri. Is do 2 directory on Xorg tree, one with the code before 2005-01-01 and other for kernel 2.6 thanks, -- Sérgio M.B. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
