All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
To: "Hanno Böck" <hanno-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Any effort on tegra?
Date: Wed, 20 Apr 2011 01:28:30 +0200	[thread overview]
Message-ID: <1303255710.2295.4.camel@workstation> (raw)
In-Reply-To: <20110420005915.4f91fcfe@laverne>

Am Mittwoch, den 20.04.2011, 00:59 +0200 schrieb Hanno Böck:
> Hi,
> 
> Nvidia produces the tegra SoC-systems, a popular use is the toshiba
> ac100.
> 
> These devices have an internal graphics chip, one can get a driver from
> nvidia, but as you can guess, it's proprietary only.
> 
> I don't have any idea if these internal graphics chips are in any way
> similar to "normal" nvidia graphic cards, but wanted to ask if there's
> any effort by the nouveau-project to also support those?

No, sorry. Tegras are significantly different from normal nvidia
chipsets. Some knowledge can be applied, but it's likely easier to write
a new driver for tegras than adapting nouveau. So there are no efforts
in supporting tegra within nouveau.

> 
> (the binary driver is a pity, as it only supports xorg-server-1.6)
> 
> _______________________________________________
> Nouveau mailing list
> Nouveau@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau


_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  reply	other threads:[~2011-04-19 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 22:59 Any effort on tegra? Hanno Böck
2011-04-19 23:28 ` Lucas Stach [this message]
2011-04-20  0:11   ` Hanno Böck
2011-04-20  7:49     ` Martin Peres

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1303255710.2295.4.camel@workstation \
    --to=dev-8ppwabl0hbeelga04laivw@public.gmane.org \
    --cc=hanno-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.