On 21.05.2012 16:58, Thierry Reding wrote:
> I agree that reflecting the hardware hierarchy within the device tree makes
> sense. I'll need to add some code to tear down child devices in the cleanup
> path, but that shouldn't be too difficult.
>
> However, adding a whole bus_type implementation
On Wed, Apr 25, 2012 at 2:45 AM, Thierry Reding
wrote:
> This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
> currently has rudimentary GEM support and can run a console on the
> framebuffer as well as X using the xf86-video-modesetting driver. Only
> the RGB output is supported.
On 21.05.2012 16:58, Thierry Reding wrote:
I agree that reflecting the hardware hierarchy within the device tree makes
sense. I'll need to add some code to tear down child devices in the cleanup
path, but that shouldn't be too difficult.
However, adding a whole bus_type implementation would
On Wed, Apr 25, 2012 at 2:45 AM, Thierry Reding
thierry.red...@avionic-design.de wrote:
This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
currently has rudimentary GEM support and can run a console on the
framebuffer as well as X using the xf86-video-modesetting driver. Only
* Terje Bergstr?m wrote:
> On 21.05.2012 14:05, Thierry Reding wrote:
>
> > I agree. It's really just a "simple-bus" kind of bus. Except that it'll need
> > another compatible value to make the host1x driver bind to it. But we should
> > be able to make it work without creating a completely new
On 21.05.2012 14:05, Thierry Reding wrote:
> I agree. It's really just a "simple-bus" kind of bus. Except that it'll need
> another compatible value to make the host1x driver bind to it. But we should
> be able to make it work without creating a completely new bus. I guess the
> "ranges" property
* Stephen Warren wrote:
> On 05/07/2012 02:50 AM, Terje Bergstr?m wrote:
> > Hi Thierry,
> >
> > I have still lots of questions regarding how device trees work. I'm now
> > just trying to match the device tree structure with hardware - let me
> > know if that goes wrong.
> >
> > There's a
* Stephen Warren wrote:
On 04/25/2012 03:45 AM, Thierry Reding wrote:
This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
currently has rudimentary GEM support and can run a console on the
framebuffer as well as X using the xf86-video-modesetting driver. Only
the RGB output
* Stephen Warren wrote:
On 05/07/2012 02:50 AM, Terje Bergström wrote:
Hi Thierry,
I have still lots of questions regarding how device trees work. I'm now
just trying to match the device tree structure with hardware - let me
know if that goes wrong.
There's a hierarchy in the
On 21.05.2012 14:05, Thierry Reding wrote:
I agree. It's really just a simple-bus kind of bus. Except that it'll need
another compatible value to make the host1x driver bind to it. But we should
be able to make it work without creating a completely new bus. I guess the
ranges property could
* Terje Bergström wrote:
On 21.05.2012 14:05, Thierry Reding wrote:
I agree. It's really just a simple-bus kind of bus. Except that it'll need
another compatible value to make the host1x driver bind to it. But we should
be able to make it work without creating a completely new bus. I
On 05/07/2012 02:50 AM, Terje Bergström wrote:
On 25.04.2012 12:45, Thierry Reding wrote:
+/ {
+ ...
+
+ /* host1x */
+ host1x: host1x@5000 {
+ compatible = nvidia,tegra20-host1x;
+ reg = 0x5000 0x00024000;
+ interrupts
On 25.04.2012 12:45, Thierry Reding wrote:
> +/ {
> + ...
> +
> + /* host1x */
> + host1x: host1x at 5000 {
> + compatible = "nvidia,tegra20-host1x";
> + reg = <0x5000 0x00024000>;
> + interrupts = <0 64 0x04 /* cop syncpt */
>
On 05/07/2012 02:50 AM, Terje Bergstr?m wrote:
> On 25.04.2012 12:45, Thierry Reding wrote:
>
>> +/ {
>> + ...
>> +
>> + /* host1x */
>> + host1x: host1x at 5000 {
>> + compatible = "nvidia,tegra20-host1x";
>> + reg = <0x5000 0x00024000>;
>> +
On 25.04.2012 12:45, Thierry Reding wrote:
+/ {
+ ...
+
+ /* host1x */
+ host1x: host1x@5000 {
+ compatible = nvidia,tegra20-host1x;
+ reg = 0x5000 0x00024000;
+ interrupts = 0 64 0x04 /* cop syncpt */
+
On 04/25/2012 03:45 AM, Thierry Reding wrote:
> This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
> currently has rudimentary GEM support and can run a console on the
> framebuffer as well as X using the xf86-video-modesetting driver. Only
> the RGB output is supported.
>
> HDMI
On 04/25/2012 03:45 AM, Thierry Reding wrote:
This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
currently has rudimentary GEM support and can run a console on the
framebuffer as well as X using the xf86-video-modesetting driver. Only
the RGB output is supported.
HDMI
This commit adds a very basic DRM driver for NVIDIA Tegra SoCs. It
currently has rudimentary GEM support and can run a console on the
framebuffer as well as X using the xf86-video-modesetting driver. Only
the RGB output is supported.
HDMI support was taken from NVIDIA's Linux kernel tree but it
18 matches
Mail list logo
