linux-kernel - Re: [PATCH] gma500: Intel GMA500 staging driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110224121042.6fa3fe37@lxorguk.ukuu.org.uk>
Date:	Thu, 24 Feb 2011 12:10:42 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Dave Airlie <airlied@...il.com>
Cc:	Alan Cox <alan@...ux.intel.com>, greg@...ah.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gma500: Intel GMA500 staging driver

> So where do we want to go my opinion is
> 
> a) remove all userspace interfaces and simplify ttm memory management usage.

Some of them appear to be valid/sensible ones for querying mode data and
config bits. I'm slowly pruning out the rest

> b) add support to hook this up to the dumb ioctl so we can do trivial
> generic front buffer allocation, so then a libkms + dumb kms
> modesetting driver can work on it.

What sort of dumb ioctl do you have in mind ?

> c) figure out how to add interface for acceleration users. Whether TTM
> fence interfaces are required etc.

The fencing seems to be solely for the various capture/acceleration bits
for video as far as I can tell.

It seems we need two things - issue a 2D command and stuff for
transferring objects, although it's not clear that the latter is needed.

The old X 2D code is at:
http://git.moblin.org/cgit.cgi/deprecated/xf86-video-psb/

> We could probably just add a GEM style buffer allocation interface but
> we'd probably need to do a lot of RE first to figure out what best
> suits the hardware, I'm pretty sure I've haven't heard any glowing
> praise that the current interface suits the hw or is maintainable.

Nor me

I'll push the 2D bits to the tree but disabled (right now they go pop and
I've not pinned down what register or other incantation I've missed
somewhere) so there is a better view of what is needed.

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