On Fri, 2009-11-13 at 12:30 -0600, Victor Lowther wrote:
> On Nov 13, 2009, at 7:30 AM, Martin Pitt wrote:
>
> > Hello Victor, hello Richard, hello devkitters,
> >
> > in the past half year we have come quite far with the "halsectomy",
> > i.e. deprecating hal [1]. The main two remaining items ar
On Fri, Nov 13, 2009 at 12:35:36PM -0600, Victor Lowther wrote:
> You are writing off a lot of legacy hardware that is probably still in
> use, as well as everything that is not intel, radeon, or nvidia. The
> quirks database should stay in some form.
I don't see how legacy hardware fits into
On Nov 13, 2009, at 10:21 AM, Matthew Garrett
wrote:
> On Fri, Nov 13, 2009 at 05:15:36PM +0100, Michael Biebl wrote:
>
>> What is the current status of KMS for radeon and noveau? Is radeon
>> KMS
>> still marked as experimental?
>
> It's marked as experimental, but only because the ABI isn't
On Nov 13, 2009, at 7:30 AM, Martin Pitt wrote:
> Hello Victor, hello Richard, hello devkitters,
>
> in the past half year we have come quite far with the "halsectomy",
> i.e. deprecating hal [1]. The main two remaining items are now X.org
> input devices (where a patch is already being discu
On Fri, Nov 13, 2009 at 05:15:36PM +0100, Michael Biebl wrote:
> What is the current status of KMS for radeon and noveau? Is radeon KMS
> still marked as experimental?
It's marked as experimental, but only because the ABI isn't fixed yet.
It should work. nouveau KMS works fine, including suspend
2009/11/13 Matthew Garrett :
> Bear in mind that with current kernels, resume should work without
> quirks on all intel and radeon, and will basically never do anything
> useful on nvidia. These are very much a legacy holdover, and at this
> point I'd recommend dropping support for them entirely.
On Fri, 2009-11-13 at 15:03 +, Matthew Garrett wrote:
> Bear in mind that with current kernels, resume should work without
> quirks on all intel and radeon, and will basically never do anything
> useful on nvidia. These are very much a legacy holdover, and at this
> point I'd recommend dropp
2009/11/13 Matthew Garrett :
> useful on nvidia. These are very much a legacy holdover, and at this
> point I'd recommend dropping support for them entirely. The market share
> of everyone else put together is miniscule, and if they're not
> interested in supporting Linux properly then we shouldn't
Bear in mind that with current kernels, resume should work without
quirks on all intel and radeon, and will basically never do anything
useful on nvidia. These are very much a legacy holdover, and at this
point I'd recommend dropping support for them entirely. The market share
of everyone else
Hello Danny,
I don't think I ever got an answer to my original mail or to the mail
below (which you can find in full at
http://lists.freedesktop.org/archives/hal/2009-August/013560.html ).
Can we go ahead with reflattening this file ? This would let us go
forward with media-player-info while keepi
Hello Victor, hello Richard, hello devkitters,
in the past half year we have come quite far with the "halsectomy",
i.e. deprecating hal [1]. The main two remaining items are now X.org
input devices (where a patch is already being discussed), and the
suspend quirks in pm-utils.
I would like to pus
11 matches
Mail list logo
