All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@seznam.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: paulus@samba.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] OF: Fix coding style violation in of_device.c and of_platform.c
Date: Mon, 05 May 2008 08:33:19 +0200	[thread overview]
Message-ID: <481EAA2F.7060101@seznam.cz> (raw)
In-Reply-To: <200805042142.45872.arnd@arndb.de>

Hi Arnd,

>> this is question to powerpc guys not to me. I haven't tried to compiled but I
>> think dcr.h is important header for powerpc.
>> I only fixed problem for Microblaze because we don't have these headers.
> 
> A google search on "microblaze DCR" shows a number of results, leading me to
> the conclusion that microblaze actually does have DCR registers. In that
> case, the best option should be to just implement a dcr.h based on 
> asm-powerpc/dcr-native.h.

You are right. Google can find a lot of things. :-)

Microblaze doesn't have any DCR instruction. If you want to use DCR you will
have to add bridge to design but I think 99,5% of designs don't have it. (Maybe
older from EDK 6 had).

Michal

  reply	other threads:[~2008-05-05  6:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 14:22 Moving OF firware to arch independent folder monstr
2008-05-03 14:22 ` [PATCH 1/2] OF: Fix coding style violation in of_device.c and of_platform.c monstr
2008-05-03 14:22   ` [PATCH 2/2] OF: Move of_device.c and of_platform.c to drivers/of/ monstr
2008-05-03 21:04   ` [PATCH 1/2] OF: Fix coding style violation in of_device.c and of_platform.c Arnd Bergmann
2008-05-04  8:20     ` Michal Simek
2008-05-04 19:42       ` Arnd Bergmann
2008-05-05  6:33         ` Michal Simek [this message]
2008-05-04 23:56   ` Stephen Rothwell
2008-05-05  0:06     ` David Miller
2008-05-06  8:57       ` Michal Simek

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=481EAA2F.7060101@seznam.cz \
    --to=monstr@seznam.cz \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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.