linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike <michael.heltne@gmail.com>
To: "Herminio Hernandez, Jr." <herminio.hernandezjr@gmail.com>
Cc: Pranith Kumar <bobby.prani@gmail.com>,
	"open list:LINUX FOR POWERPC..." <linuxppc-dev@lists.ozlabs.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: PowerPC agpmode issues
Date: Fri, 5 Feb 2016 18:06:07 +0000	[thread overview]
Message-ID: <CANtoAtM4SidDfb-pMJAB7qw-zTOSLxNjivS7gDGqj2b3-rUuPQ@mail.gmail.com> (raw)
In-Reply-To: <CAJRA9dzDbnuKhPnrQ7gN4pSHVTcJA=gjac=fnWm6pkd62AwW_A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3181 bytes --]

True, a permanent patch was needed, but at least we are up and running and
can identify other issues.. In the thread with the patches it is
highlighted that the drivers are broken in the first place

On 5 February 2016 at 17:51, Herminio Hernandez, Jr. <
herminio.hernandezjr@gmail.com> wrote:

> I have already applied his patches on my PowerBook running Jessie to get
> accelerated graphics. However they are only a work around and not a real
> fix so they will be committed to mesa.
>
> On Fri, Feb 5, 2016 at 8:44 AM, Mike <michael.heltne@gmail.com> wrote:
>
>> Herminio,
>>
>> Ok, take a look at this.
>> https://github.com/threader/mesa-11.1.1-ppc-r300-debian or if on stable
>> maybe this is more fitting
>> https://github.com/threader/mesa-10.6.3-ppc-r300-debian - this only
>> fixes the issue for r300 on powerpc though.
>>
>> On 5 February 2016 at 14:32, Herminio Hernandez Jr. <
>> herminio.hernandezjr@gmail.com> wrote:
>>
>>> I have been experiencing the same thing with my iBook and PowerBook.
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 4, 2016, at 8:47 PM, Mike <michael.heltne@gmail.com> wrote:
>>>
>>> Hi.
>>> Managed to get the Radeon R300 running on mesa 11.1.1 with an old 2013
>>> patch from Michel Dànzer, next problem is of course enabling agpmode,
>>> running with pci-mode with radeon.agpmode=-1 works, but is of course slow,
>>> and seems to load the cpu a lot.
>>>
>>> Upon initial investigation i could not initially believe agp could be
>>> this this broken for this long, until i found this.
>>>  "committed with Ben Skeggs on Feb 26, 2013"
>>>
>>> https://github.com/DespairFactor/bullhead/commit/650e1203c11354ba84d69ba445abc0efcfe3890a
>>>
>>> http://lxr.free-electrons.com/source/drivers/gpu/drm/nouveau/nouveau_agp.c?v=4.2
>>> #ifdef __powerpc__
>>> /* Disable AGP by default on all PowerPC machines for
>>> * now -- At least some UniNorth-2 AGP bridges are
>>> * known to be broken: DMA from the host to the card
>>> * works just fine, but writeback from the card to the
>>> * host goes straight to memory untranslated bypassing
>>> * the GATT somehow, making them quite painful to deal
>>> * with...
>>> */
>>> if (nouveau_agpmode == -1)
>>> return false;
>>> #endif
>>>
>>>  and now later this:
>>>
>>> https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c
>>> #ifdef __powerpc__
>>> /* Disable AGP by default on all PowerPC machines for now -- At
>>> * least some UniNorth-2 AGP bridges are known to be broken:
>>> * DMA from the host to the card works just fine, but writeback
>>> * from the card to the host goes straight to memory
>>> * untranslated bypassing that GATT somehow, making them quite
>>> * painful to deal with...
>>> */
>>> mode = 0;
>>> #endif
>>>
>>> All seems to point to serious issues had around the time of change to
>>> ums to kms and a serious regression hitting the linux kernel? No?
>>>
>>> Cheers
>>> -Mike
>>>
>>> _______________________________________________
>>> Linuxppc-dev mailing list
>>> Linuxppc-dev@lists.ozlabs.org
>>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>>>
>>>
>>
>

[-- Attachment #2: Type: text/html, Size: 6832 bytes --]

  reply	other threads:[~2016-02-05 18:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05  2:47 PowerPC agpmode issues Mike
2016-02-05  7:49 ` Denis Kirjanov
2016-02-05 14:42   ` Mike
2016-02-05 14:32 ` Herminio Hernandez Jr. 
2016-02-05 14:44   ` Mike
2016-02-05 17:51     ` Herminio Hernandez, Jr.
2016-02-05 18:06       ` Mike [this message]
2016-02-05 18:08         ` Herminio Hernandez, Jr.
2016-02-05 19:44           ` Mike
2016-02-05 19:46             ` Herminio Hernandez, Jr.
2016-02-05 19:59               ` Mike
2016-02-05 20:10                 ` Herminio Hernandez, Jr.
2016-08-25  3:09   ` Mike
2016-08-25  5:34     ` Mathieu Malaterre
2016-08-25 10:54     ` Benjamin Herrenschmidt
     [not found]       ` <57DF23C4.20508@gmail.com>
2016-09-19  9:13         ` Herminio Hernandez, Jr.
2016-09-19 10:38           ` Benjamin Herrenschmidt
2016-09-19 19:30             ` Herminio Hernandez, Jr.
2016-09-19 12:36           ` Mathieu Malaterre
2016-09-20  3:05             ` Michel Dänzer
2016-09-20  3:43               ` Herminio Hernandez, Jr.
2016-09-20  6:20                 ` Michel Dänzer
2016-09-21  6:20                   ` Herminio Hernandez, Jr.
2016-10-08 19:05                     ` Herminio Hernandez, Jr.
2016-10-09  7:49                       ` Benjamin Herrenschmidt
2016-02-08  9:53 ` Michel Dänzer
2016-02-08 12:09   ` Mike
2016-02-08 12:41   ` Boris Reinhard
2016-02-08 13:28     ` Mike
2016-02-09  1:41       ` Michel Dänzer
2016-02-09  2:27         ` Mike
2016-02-09 11:52           ` Gerhard Pircher
2016-02-09 12:15             ` luigi burdo

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=CANtoAtM4SidDfb-pMJAB7qw-zTOSLxNjivS7gDGqj2b3-rUuPQ@mail.gmail.com \
    --to=michael.heltne@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bobby.prani@gmail.com \
    --cc=herminio.hernandezjr@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).