[lkml]   [2006]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/2]Blackfin archtecture patche for 2.6.16
  Thanks for your reply. See below.

On 3/21/06, Andrew Morton <> wrote:
> "Luke Yang" <> wrote:
> >
> > This is the Blackfin archtecture patch for kernel 2.6.16.
> >
> There are few practical issues we need to be concerned about with new
> architectures.
> - We don't want to be putting 44000 lines of new code in the kernel and
> then have it rot. Who will support this in the long-term? What
> resources are behind it? IOW: what can you say to convince us that it
> won't rot?
> The lack of a MAINTAINERS entry doesn't inspire confidence..
As Bernd said, Analog Device has a group maintaining linux for
Blackfin. Now I am the one who in charge of committing patches into
mainline, other developers may do the same thing later. By
MAINTAINERS entry do you mean the linux-2.6/MAINTAINER? Or shall I
list maintainers name in the patch mail?
> - How widespread/popular is the blackfin? Are many devices using it?
> How old/mature is it? Is it a new thing or is it near end-of-life?
As a DSP, Blackfin has been there for years and is somewhat popular.
But as a CPU which can run Linux, we are trying to make it popular.
Anyway a 5$ chip runs Linux and can do audio/video codec is a good toy
to play with.
> It's a cost/benefit thing. It costs us to add code to the kenrel. How
> many people would benefit from us doing that?
As multimedia is becoming popular in embedded world, I believe many
people would benefit from a DSP running Linux.
> - Are easy-to-install x86 cross-build packages available? If not, are
> there straightforward instructions anywhere to guide people in generating
> a cross-build setup? is a good place to find documents.
In my opinion, not many CPU has such good documents site. Even a
beginner will find it as a good linux and embedded training place.
> <looks>
> OK, seems to have that. Does binutils support
> blackfin?
> - A lot of this code appears to come from Analog Devices, but you don't ;)
Actually I am. Just perfer gmail than outlook web (I don't use
window$, so don't have outlook to access company mailbox).
> We'd need to see some sort of authorisation from the original authors
> for the inclusion of their code. Preferably in the form of
> Signed-off-by:s.
For this patch it is Luke Yang, then for other drivers or patches,
it would be the maintainer. All our work(software or even hardware) is
opened, our group don't do any un-GPLed software now.
> >
> As I said, 44kloc ;)
Sorry for the size, again :) But I really don't want to split it,
doesn't make much sense.
> - Do you really need to support old_mmap()?
> - It would be preferable to use the generic IRQ infrastructure in kernel/irq/
Task added. I'll make it happen.
> - Too much use of open-coded `volatile'. The objective should be to have
> zero occurrences in .c files. And volatile sometimes creates suspicion
> even when it's used in .h files.
volatile is not evil :) The only and correct usage is variables that
may be modified by hardware (such as MMR) or in a irq/signal handler.
I have checked my code. Yes some kind of warpper may look better, we
have plan to change it, I'll send you patch for this.
> - bug: coreb_ioctl() does copy_from_user() and down() inside spinlock.
> - err, coreb_ioctl() does down(&file->f_dentry->d_inode->i_sem); but
> that's a mutex now, so I assume that's actually dead code?
Thanks. Bug reported. Actually that's part of the reasons we want
to get into mainline: As we keep up to latest kernel, we can get rid
of the obsolete code in time.

Best regards,
Luke Yang;
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-03-22 04:48    [W:0.080 / U:6.888 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site