The pull request you sent on Thu, 18 Jul 2024 15:40:08 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-next-2024-07-18
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b3ce7a30847a54a7f96a35e609303d8afecd460b
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The pull request you sent on Tue, 7 Nov 2023 12:03:00 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2023-11-07
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/25b6377007ebe1c3ede773fd6979f613386db000
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
Hi Linus,
Geert pointed out I missed the renesas reworks in my main pull, so
this pull contains the renesas next work for atomic conversion and DT
support. It also contains a bunch of amdgpu and some small ssd13xx
fixes.
I'm going to be travelling from tomorrow, I should in theory have
access to
The pull request you sent on Thu, 27 Apr 2023 11:43:17 +1000:
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/32f7ad0fbe7521de2a5e8f79c33d46110247fd7c
Thank you!
--
Deet-doot-dot, I am a bot.
htt
Hi Linus,
A bit out of routine fixes pull for rc1, there's a build breakage on
some platforms due to ttm, this has that fix + qaic uapi removal +
minor panel fixes.
Dave.
drm-next-2023-04-27:
drm-next fixes for 6.4-rc1
ttm:
- Fix TTM build on archs where PMD_SHIFT is not constant.
qaic:
- Rever
The pull request you sent on Fri, 3 Mar 2023 09:07:58 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2023-03-03-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2eb29d59ddf02e39774abfb60b2030b0b7e27c1f
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
Hi Linus,
This is the fixes for the last couple of weeks on top of the drm-next,
I don't think this contains any next content it should be all fixes.
amdgpu and i915 mostly, the amdgpu ones are bigger because it's two
weeks in one.
hopefully this week I got the subject line right.
Dave.
drm-nex
>
> Christ. It's been two weeks. I'm doing -rc4 today, and I still don't
> have the fix.
>
> The problem seems entirely obvious, as reported by Kirill: the nv50
> code unconditionally calls the "atomic_{dis,en}able()" functions, even
> when not everybody was converted.
>
> The fix seems to be to ei
On Mon, 16 Nov 2020 at 03:57, Linus Torvalds
wrote:
>
> On Tue, Nov 3, 2020 at 2:20 PM Kirill A. Shutemov
> wrote:
> >
> > On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> > > drm/nouveau/kms: Search for encoders' connectors properly
> >
> > This commit (09838c4efe9a) broke b
On Tue, Nov 3, 2020 at 2:20 PM Kirill A. Shutemov wrote:
>
> On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> > drm/nouveau/kms: Search for encoders' connectors properly
>
> This commit (09838c4efe9a) broke boot for me. These two hunks in
> particular:
Christ. It's been two we
On 2020/10/15 9:33, Dave Airlie wrote:
> drm/vram-helper: stop using TTM placement flags
This commit (7053e0eab473) produce call trace for me as below:
[ 64.782340] WARNING: CPU: 51 PID: 1964 at
drivers/gpu/drm/drm_gem_vram_helper.c:284 drm_gem_vram_offset+0x35/0x40
[drm_vram_helper]
[
JFYI-looking at this today
On Mon, 2020-11-09 at 14:52 +0300, Kirill A. Shutemov wrote:
> On Wed, Nov 04, 2020 at 04:58:14PM -0500, Lyude Paul wrote:
> > ACK, I will send out a patch for this asap
>
> Any update. AFAICS, v5.10-rc3 is still buggy.
>
--
Sincerely,
Lyude Paul (she/her)
Soft
whoops, you can ignore this actually - I got this mixed up with an Intel issue I
was looking at, this is actually a nouveau issue and you guys don't need to look
at this :)
Kirill-I'll get to this asap, but I've got some other stuff on my plate to go
through first. Could you open up a bug on gitla
On Mon, Nov 09, 2020 at 12:50:48PM -0500, Lyude Paul wrote:
> Looking at the patches you sent is on my TODO list for this week at least as a
> priority, although I really would have hoped that someone from Intel would
> have looked by now since it's a regression on their end.
What regression are y
Looking at the patches you sent is on my TODO list for this week at least as a
priority, although I really would have hoped that someone from Intel would
have looked by now since it's a regression on their end.
Gentle ping to Vsyrjala and Imre
On Mon, 2020-11-09 at 14:52 +0300, Kirill A. Shutemov
On Wed, Nov 04, 2020 at 04:58:14PM -0500, Lyude Paul wrote:
> ACK, I will send out a patch for this asap
Any update. AFAICS, v5.10-rc3 is still buggy.
--
Kirill A. Shutemov
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freed
ACK, I will send out a patch for this asap
On Wed, 2020-11-04 at 01:20 +0300, Kirill A. Shutemov wrote:
> On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> > drm/nouveau/kms: Search for encoders' connectors properly
>
> This commit (09838c4efe9a) broke boot for me. These two hu
On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> drm/nouveau/kms: Search for encoders' connectors properly
This commit (09838c4efe9a) broke boot for me. These two hunks in
particular:
@ -2066,7 +2120,7 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state
*state)
On Fri, 16 Oct 2020 at 04:42, Linus Torvalds
wrote:
>
> On Thu, Oct 15, 2020 at 10:51 AM Linus Torvalds
> wrote:
> >
> > Thanks, looks good to me [..]
>
> Uhhuh. I already pushed things out, but my clang build (which I don't
> do between each merge) shows a problem:
>
> drivers/gpu/drm/amd/amdg
On Thu, Oct 15, 2020 at 10:51 AM Linus Torvalds
wrote:
>
> Thanks, looks good to me [..]
Uhhuh. I already pushed things out, but my clang build (which I don't
do between each merge) shows a problem:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:650:8:
warning: logical
The pull request you sent on Thu, 15 Oct 2020 11:33:08 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2020-10-15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/93b694d096cc10994c817730d4d50288f9ae3d66
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
On Wed, Oct 14, 2020 at 6:33 PM Dave Airlie wrote:
>
> There are a bunch of conflicts but none of them seemed overly scary,
> and sfr has provided resolutions for them all. I've put a tree up with
> my merge results, so you can tell me I did it wrong here:
> https://cgit.freedesktop.org/~airlied/
On Thu, Oct 15, 2020 at 10:53:28AM -0400, Alex Deucher wrote:
> On Thu, Oct 15, 2020 at 9:59 AM Peilin Ye wrote:
> > It has been applied to linux-next twice, for unknown reasons. Thank you!
>
> The patch was already in drm-next, but since it was a bug fix it was
> applied it to 5.9 as well.
Ah,
On Thu, Oct 15, 2020 at 9:59 AM Peilin Ye wrote:
>
> Hi all,
>
> On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> > Peilin Ye (1):
> > drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl()
>
> This patch is already in mainline:
>
> commit 543e8669ed9bfb30545fd52bc0e047ca4d
Hi all,
On Thu, Oct 15, 2020 at 11:33:08AM +1000, Dave Airlie wrote:
> Peilin Ye (1):
> drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl()
This patch is already in mainline:
commit 543e8669ed9bfb30545fd52bc0e047ca4df7fb31
Author: Peilin Ye
Date: Tue Jul 28 15:29:24 2020 -0400
On Thu, 15 Oct 2020 at 11:33, Dave Airlie wrote:
>
> Hi Linus,
>
> This is the main drm pull request for 5.10.
>
> Not a major amount of change, the i915 trees got split into display
> and gt trees to better facilitate higher level review, and there's a
> major refactoring of i915 GEM locking to u
On Tue, 11 Aug 2020 at 04:46, Dave Airlie wrote:
>
> On Mon, 10 Aug 2020 at 22:23, Christoph Hellwig wrote:
> >
> > On Thu, Aug 06, 2020 at 11:07:02AM +1000, Dave Airlie wrote:
> > > nouveau:
> > > - add CRC support
> > > - start using NVIDIA published class header files
> >
> > Where does Nvdia
On Mon, 10 Aug 2020 at 22:23, Christoph Hellwig wrote:
>
> On Thu, Aug 06, 2020 at 11:07:02AM +1000, Dave Airlie wrote:
> > nouveau:
> > - add CRC support
> > - start using NVIDIA published class header files
>
> Where does Nvdia provide them? I looked into the commits and the
> Nouveau mailing l
The pull request you sent on Thu, 6 Aug 2020 11:07:02 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2020-08-06
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8186749621ed6b8fc42644c399e8c755a2b6f630
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
On Thu, 6 Aug 2020 at 11:07, Dave Airlie wrote:
>
> Hi Linus,
>
> This the main drm pull request for 5.9-rc1.
>
> New xilinx displayport driver, AMD support for two new GPUs (more
> header files), i915 initial support for RocketLake and some work on
> their DG1 (discrete chip).
>
> The core also g
The pull request you sent on Mon, 8 Jun 2020 13:15:58 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2020-06-08
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/107821669a9cbf234f260d576039983b64c7cb6d
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
Hey Linus,
This are the fixes from last week for the stuff merged in the merge
window. It got a bunch of nouveau fixes for HDA audio on some new
GPUs, some i915 and some amdpgu fixes.
I've got another pull request with Rob's msm next stuff in it I'll
send along after this, it was in -next all alo
The pull request you sent on Sat, 5 Jan 2019 05:10:22 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2019-01-05
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0fe4e2d5cd931ad2ff99d61cfdd5c6dc0c3ec60b
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
Hi Linus,
Happy New Year, just decloaking from leave to get this stuff in before rc1.
Some stuff from the last week:
core:
two regression fixes for damage blob and atomic
i915 gvt:
Some missed GVT fixes from the original pull
amdgpu:
new PCI IDs
SR-IOV fixes
DC fixes
Vega20 fixes
Dave.
drm-ne
The pull request you sent on Thu, 27 Dec 2018 10:09:49 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2018-12-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7e59fad9c9d1aeacdc96dfffd35f9e12ddc34dbf
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
Hi Linus,
Daniel collected a couple of pulls after I want on holidays, back for
a couple of days, so may as well send them out.
This has exynos and etnaviv work for 4.21.
exynos:
- plane alpha and blending configurability
etnaviv:
- mostly cleanups in prep for new features.
Dave.
drm-next-201
On Thu, Nov 1, 2018 at 10:32 PM Dave Airlie wrote:
>
> Pretty much a normal fixes pull pre-rc1, mostly amdgpu fixes, one i915
> link training regression fix, and a couple of minor panel/bridge fixes
> and a panel quirk.
Pulled,
Linus
Hi Linus,
Pretty much a normal fixes pull pre-rc1, mostly amdgpu fixes, one i915
link training regression fix, and a couple of minor panel/bridge fixes
and a panel quirk.
Thanks,
Dave.
drm-next-2018-11-02:
drm, i915, amdgpu, bridge + core quirk
The following changes since commit f2bfc71aee75feff
Hi Linus,
I looked at Rob's msm tree, he kept it small due to being late, and it
was in -next for a while before he was ill, so I think it should be
fine. Otherwise this contains a set of i915 fixes and a v3d build fix,
and vc4 leak fix.
Thanks,
Dave.
drm-next-2018-06-11:
msm next, i915, vc4, v3
On Tue, Nov 08, 2016 at 01:41:08PM +, Liviu Dudau wrote:
> On Tue, Nov 08, 2016 at 01:49:55PM +0100, Daniel Vetter wrote:
> > On Tue, Nov 08, 2016 at 12:26:19PM +, Liviu Dudau wrote:
> > > Hi Dave,
> > >
> > > Here is the list of fixes that I have for drm/mali-dp. They've been on
> > > th
On Tue, Nov 08, 2016 at 12:26:19PM +, Liviu Dudau wrote:
> Hi Dave,
>
> Here is the list of fixes that I have for drm/mali-dp. They've been on the
> mailing
> lists for a while and merged into linux-next for a few weeks, but due to
> holiday and
> travel to Linux Plumbers I did not send the
On Tue, Nov 08, 2016 at 01:49:55PM +0100, Daniel Vetter wrote:
> On Tue, Nov 08, 2016 at 12:26:19PM +, Liviu Dudau wrote:
> > Hi Dave,
> >
> > Here is the list of fixes that I have for drm/mali-dp. They've been on the
> > mailing
> > lists for a while and merged into linux-next for a few week
Hi Dave,
Here is the list of fixes that I have for drm/mali-dp. They've been on the
mailing
lists for a while and merged into linux-next for a few weeks, but due to
holiday and
travel to Linux Plumbers I did not send the pull request earlier. I don't know
if
these patches can be pulled into v4.
Hi Dave,
I would like to add the Mali DP driver to the drm-next tree.
It has got several reviews and now the Acks from the relevant people.
The tree is based on drm-intel/topic/drm-misc tree with tag
topic/drm-misc-2016-06-14 and also needs two patches from Daniel to
function correctly [1][2]. H
On Wed, Jan 13, 2016 at 01:13:07PM +, Liviu Dudau wrote:
> Hi David,
Gentle ping! Are there any reasons not to include this series into drm-next? It
has
been cooking (rotting?) in linux-next for more than a month now.
I'm aware of the cleanup of .preclose hook that Daniel Vetter has on a dif
Hi David,
This is the DRM part of the ARM HDLCD driver. It has been included in
linux-next for about a week and includes the Kconfig patches submitted
by Arnd Bergman last week. Please pull into drm-next.
Best regards,
Liviu
The following changes since commit 8a0d560f3e651808ae0a3d9ab9fe476e59de
Hi Linus,
The sti driver had a requirement on some patches in Greg's tree, they are
in, so I see no problems just merging this one now. But if it's too late
I don't mind either.
Dave.
The following changes since commit a18e2fa5e670a1b84e66522b221c42875b02028a:
Merge tag 'arm64-fixes' of
gi
On Fri, 7 Feb 2014, Daniel Vetter wrote:
> Sorry for missing your report here. Before we disable this again for
> gen4 I want to make sure that it's the same irq misrouting issue which
> was already the cause for the gmbus irq mess. Can you please boot with
> pci=nomsi (so that i915 uses irq16)?
>
On Fri, Feb 7, 2014 at 2:40 PM, Jiri Kosina wrote:
> On Fri, 7 Feb 2014, Jani Nikula wrote:
>
>> >> > git://people.freedesktop.org/~airlied/linux drm-next
>> >> [ ... snip ... ]
>> >> > Daniel Vetter (59):
>> >> [ ... snip ... ]
>> >> > drm/i915: dp aux irq support for g4x/vlv
>> >>
>> >>
On Fri, 7 Feb 2014, Jani Nikula wrote:
> >> > git://people.freedesktop.org/~airlied/linux drm-next
> >> [ ... snip ... ]
> >> > Daniel Vetter (59):
> >> [ ... snip ... ]
> >> > drm/i915: dp aux irq support for g4x/vlv
> >>
> >> This commit causes all kinds of havoc on my ThinkPad x200s. I
On Fri, 07 Feb 2014, Jiri Kosina wrote:
> On Thu, 30 Jan 2014, Jiri Kosina wrote:
>
>> > git://people.freedesktop.org/~airlied/linux drm-next
>> [ ... snip ... ]
>> > Daniel Vetter (59):
>> [ ... snip ... ]
>> > drm/i915: dp aux irq support for g4x/vlv
>>
>> This commit causes all kinds o
On Thu, 30 Jan 2014, Jiri Kosina wrote:
> > git://people.freedesktop.org/~airlied/linux drm-next
> [ ... snip ... ]
> > Daniel Vetter (59):
> [ ... snip ... ]
> > drm/i915: dp aux irq support for g4x/vlv
>
> This commit causes all kinds of havoc on my ThinkPad x200s. It results in
[ ... s
On Thu, 30 Jan 2014, Dave Airlie wrote:
> git://people.freedesktop.org/~airlied/linux drm-next
[ ... snip ... ]
> Daniel Vetter (59):
[ ... snip ... ]
> drm/i915: dp aux irq support for g4x/vlv
This commit causes all kinds of havoc on my ThinkPad x200s. It results in
irq 16: nobody care
Dave Airlie schreef op do 30-01-2014 om 02:49 [+]:
> Christian K?nig (10):
> [...]
> drm/radeon: add GART debugfs access v3
> [...]
That one generates a bit of (warning) noise when building on 32 bits
x86:
In file included from include/asm-generic/bug.h:13:0,
Hi Linus,
Been a bit busy, first week of kids school, and waiting on other trees to go in
before I could send this, so its a bit later than I'd normally like.
For some reason the request-pull and the merge into your tree look different,
since some of the changes in this have already gone in via
On Wed, Jan 29, 2014 at 6:49 PM, Dave Airlie wrote:
>
> For some reason the request-pull and the merge into your tree look different,
> since some of the changes in this have already gone in via the arm-soc tree
> and dma stuff, all for tegra. Hopefully nobody rebased when they shouldn't.
Looks m
Hi Linus,
This is the one and only next pull for 3.8, we had a regression we found
last week, so I was waiting for that to resolve itself, and I ended up
with some Intel fixes on top as well.
Highlights:
new driver: nvidia tegra 20/30/hdmi support
radeon: add support for previously unused DMA
On Wed, Mar 23, 2011 at 8:33 AM, Jesse Barnes wrote:
>
> Chris mentioned a7a75c8f7 on irc, not sure if it was regarding this
> issue though, but it does seem a likely candidate.
Yup, that revert fixes it for me.
Linus
___
dri-devel mail
On Wed, Mar 23, 2011 at 8:33 AM, Jesse Barnes
wrote:
>
> Chris mentioned a7a75c8f7 on irc, not sure if it was regarding this
> issue though, but it does seem a likely candidate.
Yup, that revert fixes it for me.
Linus
On Wed, Mar 23, 2011 at 3:19 AM, Linus Torvalds
wrote:
> So I had ?hoped - yes, very na?ve of me, I know - that this merge
> window would be different.
>
> But it's not.
>
> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
>>
>> i915: big 855 fix, lots of output setup refactoring, lots of misc
On Wed, Mar 23, 2011 at 8:21 AM, Stephen Clark
wrote:
> On 03/22/2011 10:19 PM, Linus Torvalds wrote:
>>
>> So I had ?hoped - yes, very na?ve of me, I know - that this merge
>> window would be different.
>>
>> But it's not.
>>
>> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie ?wrote:
>>
>>>
>>> i91
On Wed, 23 Mar 2011 08:29:35 -0700
Linus Torvalds wrote:
> On Tue, Mar 22, 2011 at 7:19 PM, Linus Torvalds
> wrote:
> >
> > Keith/Jesse/Chris - I don't know that it's i915, and it will take
> > forever to bisect (I'll try). But it does seem pretty likely.
>
> Ok, so I'm still bisecting, but it'
On Wed, 23 Mar 2011 08:29:35 -0700
Linus Torvalds wrote:
> On Tue, Mar 22, 2011 at 7:19 PM, Linus Torvalds
> wrote:
> >
> > Keith/Jesse/Chris - I don't know that it's i915, and it will take
> > forever to bisect (I'll try). But it does seem pretty likely.
>
> Ok, so I'm still bisecting, but it'
On Tue, Mar 22, 2011 at 7:19 PM, Linus Torvalds
wrote:
>
> Keith/Jesse/Chris - I don't know that it's i915, and it will take
> forever to bisect (I'll try). But it does seem pretty likely.
Ok, so I'm still bisecting, but it's definitely the DRM pull. Current
bisection log attached (the result doe
On Tue, Mar 22, 2011 at 7:19 PM, Linus Torvalds
wrote:
>
> Keith/Jesse/Chris - I don't know that it's i915, and it will take
> forever to bisect (I'll try). But it does seem pretty likely.
Ok, so I'm still bisecting, but it's definitely the DRM pull. Current
bisection log attached (the result doe
On Wed, 23 Mar 2011 08:21:53 -0400
Stephen Clark wrote:
> On 03/22/2011 10:19 PM, Linus Torvalds wrote:
> > So I had hoped - yes, very naïve of me, I know - that this merge
> > window would be different.
> >
> > But it's not.
> >
> > On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
> >
>
On Wed, 23 Mar 2011 08:21:53 -0400
Stephen Clark wrote:
> On 03/22/2011 10:19 PM, Linus Torvalds wrote:
> > So I had hoped - yes, very na?ve of me, I know - that this merge
> > window would be different.
> >
> > But it's not.
> >
> > On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
> >
>
On 03/22/2011 10:19 PM, Linus Torvalds wrote:
> So I had hoped - yes, very na?ve of me, I know - that this merge
> window would be different.
>
> But it's not.
>
> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
>
>> i915: big 855 fix, lots of output setup refactoring, lots of misc fixes.
On Wed, Mar 23, 2011 at 3:19 AM, Linus Torvalds
wrote:
> So I had hoped - yes, very naïve of me, I know - that this merge
> window would be different.
>
> But it's not.
>
> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
>>
>> i915: big 855 fix, lots of output setup refactoring, lots of misc
On 03/22/2011 10:19 PM, Linus Torvalds wrote:
So I had hoped - yes, very naïve of me, I know - that this merge
window would be different.
But it's not.
On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
i915: big 855 fix, lots of output setup refactoring, lots of misc fixes.
.. a
On Wed, Mar 23, 2011 at 8:21 AM, Stephen Clark wrote:
> On 03/22/2011 10:19 PM, Linus Torvalds wrote:
>>
>> So I had hoped - yes, very naïve of me, I know - that this merge
>> window would be different.
>>
>> But it's not.
>>
>> On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
>>
>>>
>>> i915
So I had hoped - yes, very na?ve of me, I know - that this merge
window would be different.
But it's not.
On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wrote:
>
> i915: big 855 fix, lots of output setup refactoring, lots of misc fixes.
.. and apparently a lot of breakage too. My crappy laptop t
Hi Linus,
since I see drm named in two other pull threads (staging + bkl) I suppose
I should send my pull req.
Highlights:
core: drop i830 driver and BKL, add support to drm core to allow USB drm
drivers, generic unaccelerated buffer create/map fns for simple fbdev
applications (like plymouth
Hi Linus,
since I see drm named in two other pull threads (staging + bkl) I suppose
I should send my pull req.
Highlights:
core: drop i830 driver and BKL, add support to drm core to allow USB drm
drivers, generic unaccelerated buffer create/map fns for simple fbdev
applications (like plymouth
74 matches
Mail list logo
