LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Mantler <nicoya@apia.dhs.org>
To: mlan@cpu.lu, Franz.Sirl-kernel@lauterbach.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] VRAM detection in controlfb
Date: Sun, 4 Jun 2000 10:08:39 -0500	[thread overview]
Message-ID: <v04003a00b5602003688d@[24.66.67.194]> (raw)
In-Reply-To: <200006040709.JAA00760@piglet.grunz.lu>


At 2:09 AM -0500 6/4/2000, Michel Lanners wrote:
>Hi Franz,
>
>On   3 Jun, this message from Franz Sirl echoed through cyberspace:
>[hacking controlfb]
>> if you don't mind, would you try to replace the "dcbi" assembler
>>instructions
>> in the detection code with "dcbf" instructions? It seems Dan inherited
>>my bug
>> I had in the platinumfb driver...
>
>Sure, no problem.
>
>In what sense is that a bug, and what would be the symptom? I know close
>to nothing about PPC assembler, and fully understanding the detection
>code might help fix the detection problems we still have in some
>situations...

dcbi = data cache block invalidate. If you do this on a dirty cache block,
data will be lost.

dcbf = data cache block flush. If you do this on a block that isn't in a
coherent state, data will be lost.

If you have a block that's both dirty and incoherent... well, don't do that. :)


btw, my mail server messed up and I got bounced off the list a few weeks
back, have I missed anything interesting?


Cheers - Tony :)


--
Tony Mantler       Renaissance Nerd Extraordinaire     nicoya@apia.dhs.org
Winnipeg, Manitoba, Canada                     http://nicoya.feline.pp.se/


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-04 15:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-31 22:43 [patch] VRAM detection in controlfb Michel Lanners
2000-06-01  0:57 ` Takashi Oe
2000-06-03  6:28   ` Michel Lanners
2000-06-03  7:13     ` Takashi Oe
2000-06-03  7:30       ` Geert Uytterhoeven
2000-06-03  8:49         ` Michel Dänzer
2000-06-03  9:22           ` Geert Uytterhoeven
2000-06-06 19:25             ` Michael Schmitz
2000-06-06 21:52               ` Michel Lanners
2000-06-03  7:38     ` Geert Uytterhoeven
2000-06-05  6:01       ` Michel Lanners
2000-06-04  0:09     ` Daniel Jacobowitz
2000-06-04  0:31       ` Ani Joshi
2000-06-04 13:55         ` Michel Lanners
2000-06-05 12:59           ` Michel Dänzer
2000-06-03  9:16 ` Franz Sirl
2000-06-04  7:09   ` Michel Lanners
2000-06-04 15:08     ` Tony Mantler [this message]
2000-06-04 17:48       ` Daniel Jacobowitz
2000-06-05  5:48         ` Michel Lanners
2000-06-05 12:40           ` Tony Mantler
2000-06-05 13:51             ` Michel Lanners
2000-06-05 14:15               ` Geert Uytterhoeven
2000-06-05 23:49                 ` Tony Mantler
2000-06-06  5:15                 ` Timothy A. Seufert
2000-06-06 19:49             ` Michael Schmitz
2000-06-06 21:58               ` Michel Lanners
2000-06-07  7:59                 ` Geert Uytterhoeven
     [not found] <20000607233456Z.roikawa@rr.iij4u.or.jp>
2000-06-07 15:10 ` Geert Uytterhoeven
2000-06-07 15:20   ` Michael Schmitz
2000-06-07 15:41     ` Geert Uytterhoeven
2000-06-07 15:58   ` Ryuichi Oikawa
2000-06-07 19:11     ` Geert Uytterhoeven

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='v04003a00b5602003688d@[24.66.67.194]' \
    --to=nicoya@apia.dhs.org \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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