AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Holland <nholland-iI9p2NPcQ/rYtjvyW6yDsg@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: amdgpu: Corrupted video on 32 bit systems (possible fix)
Date: Fri, 20 Jan 2017 13:07:05 +0100	[thread overview]
Message-ID: <20170120120704.GA11366@teela.fritz.box> (raw)
In-Reply-To: <e0c4917a-8484-1cc3-8809-c8685ff0c5f1-otUistvHUpPR7s880joybQ@public.gmane.org>

On Fri, Jan 20, 2017 at 06:11:50PM +0900, Michel Dänzer wrote:
> On 20/01/17 04:44 PM, Nils Holland wrote:
> > 
> > Sounds like a good idea! I was a bit heasitant because, to be honest,
> > I'm not at all an expert about the code in question and basically only
> > saw how you fixed the issue in radeon and thought: "Well, let's see if
> > I can do the same thing in amdgpu and if so, if it helps there, too".
> > ;-)
> > 
> > However, since you've said that a 32 bit fix in amdgpu generally seems
> > like a good idea,
> 
> Actually, unless your CPU can't run 64-bit code, I'd say running a
> 64-bit kernel would be an overall even better idea for you, even with
> 32-bit userspace. :) Anyway, this problem clearly needs to be fixed.

Yep, that's certainly true! However, I have to admit that I'm
intentionally regularly testing all kinds of stuff on pure 32 bit,
because I think that most of the other "first like of testing", i.e.
the developers themselves, are primarily working with 64 bit these
days. So I thought it might make sense if someone keeps a little of an
eye on 32 bit - after all, in general and if there are no technical
reasons that speak agsinst it, things should work there, too. And
indeed, during the past year I've spotted a few little things that
were only causing problems on 32 bit - both in the kernel and other
components like systemd - and which could subsequently be fixed in a
relatively easy manner.

> > I would indeed use a little time on the weekend to get a proper patch
> > ready and submit it for review. Even if the "no wc for x86_32" part is
> > probably the only thing it'll contain
> 
> I wouldn't bother with that. There is no real reason against bringing it
> all over in one go.

Right, I'll see what I can do over the weekend. So stay tuned for my
first ever proper (at least as far as the guidelines for submitting
patches are concerned) patch and expect the worst. ;-)

Greetings
Nils
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2017-01-20 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170119193537.GA3296@teela.fritz.box>
2017-01-20  2:47 ` amdgpu: Corrupted video on 32 bit systems (possible fix) Michel Dänzer
2017-01-20  7:44   ` Nils Holland
2017-01-20  9:11     ` Christian König
2017-01-20  9:11     ` Michel Dänzer
     [not found]       ` <e0c4917a-8484-1cc3-8809-c8685ff0c5f1-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-01-20 12:07         ` Nils Holland [this message]

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=20170120120704.GA11366@teela.fritz.box \
    --to=nholland-ii9p2npcq/rytjvyw6ydsg@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox