mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luke Yang <luke.adi@gmail.com>
To: Andrey Volkov <avolkov@varma-el.com>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
	bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Mon, 14 Nov 2005 15:22:01 +0800	[thread overview]
Message-ID: <489ecd0c0511132322n4cfc0125r1358ba6136aaa0dc@mail.gmail.com> (raw)
In-Reply-To: <4375D8D4.9010605@varma-el.com>

On 11/12/05, Andrey Volkov <avolkov@varma-el.com> wrote:
> Luke Yang wrote:
> >>Does this architecture support SMP?  I see it's BROKEN_ON_SMP, but there
> >>seems to be some smp-style stuff in there.
> >
> >
> >    It doesn't support SMP now.
>
> Wrong, how about dual core BF56x subfamily? It's true SMP beast.
> Or you are try to told that "current SOFTWARE arch doesn't
> support it yet", am I right?

 Yes, BF56x does have two cores in one chip. But we are not going to
make it a SMP system. The second core is going to be used as a pure
DSP, do some encode/decode work. Remember Blackfin itself is a DSP
anyway.

>
> Also, returning to previous posts, ALL BF5xx have normal
> MMU (which possible not so useful for DSP tasks).

  Actually current BF5xx DSPs don't have a real MMU. It runs uClinux.
The called  "MMU" in the mannual is only a cache management and memory
protect unit, not a virtual memory unit.

>
> --
> Regards
> Andrey Volkov
>
>

  reply	other threads:[~2005-11-14  7:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  9:28 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02  7:06   ` Luke Yang
2005-11-04  4:59     ` Luke Yang
2005-11-04 23:06       ` Greg KH
2005-11-07  6:58         ` Luke Yang
2005-11-07 16:59           ` Greg KH
2005-11-08  7:50             ` Andrew Morton
2005-11-11 11:26               ` Luke Yang
2005-11-12 11:58                 ` Andrey Volkov
2005-11-14  7:22                   ` Luke Yang [this message]
2005-11-12 21:47                 ` Greg KH
2005-11-13 14:22                   ` Bernd Schmidt
2005-11-14  7:34                   ` Luke Yang
2005-11-14  7:52                     ` Arjan van de Ven
2005-11-15  2:40                       ` Luke Yang
2005-11-15  4:14                         ` Greg KH
2005-11-14 12:53                     ` Alan Cox
2005-11-16  3:44               ` Luke Yang
2005-11-16  6:11                 ` Paul Jackson
2005-11-16  6:34                   ` Luke Yang
2005-11-16 13:42               ` Bernd Schmidt
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET
2005-11-17  5:38 Robin Getz

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=489ecd0c0511132322n4cfc0125r1358ba6136aaa0dc@mail.gmail.com \
    --to=luke.adi@gmail.com \
    --cc=akpm@osdl.org \
    --cc=avolkov@varma-el.com \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®