[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0804231438u68118bc0t4abe8e85733b23f2@mail.gmail.com>
Date: Wed, 23 Apr 2008 17:38:53 -0400
From: "Mike Frysinger" <vapier.adi@...il.com>
To: monstr@...nam.cz
Cc: "Arnd Bergmann" <arnd@...db.de>,
"Will Newton" <will.newton@...il.com>,
"Linux Kernel list" <linux-kernel@...r.kernel.org>,
linux-arch@...r.kernel.org, git@...inx.com,
microblaze-uclinux@...e.uq.edu.au
Subject: Re: [RFC] Introduce __ARCH_WANT_SYS_SYSFS
On Wed, Apr 23, 2008 at 5:16 PM, Michal Simek <monstr@...nam.cz> wrote:
> I would like to fix syscalls in Microblaze repo. Can you give me a hint how to
> do it?
>
> I look at Blackfin arch and I compared files with microblaze. There are some
> differences but not so much.
> Can you tell me how to test it which syscall is necessary for platform.
> I have never found any documentation about.
>
> In my syscall_table.S (on some arch in entry.S) is one big jump table with
> reference to syscalls. In unistd.h is definition.
>
> Is there any convention which syscalls are use for all archs and which are
> architecture specific?
i dont believe there is any documentation for syscalls. you just have
to know which syscalls are outdated and which replace others ;). i
think someone already pointed out a few to you in an earlier post ?
otherwise, feel free to ask about sets.
i dont recall if microblaze is no-mmu-only, mmu-only, or both ... you
should take care with comparing against Blackfin if microblaze
supports an mmu. if it is no-mmu-only, then the Blackfin list should
be quite good for you start with as we turn off numa/mmu-only
functions as well as old stuff (like the poll/select/mmap/etc...
friends).
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists