From: "Mike Frysinger" <vapier.adi@gmail.com>
To: monstr@seznam.cz
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Will Newton" <will.newton@gmail.com>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, git@xilinx.com,
microblaze-uclinux@itee.uq.edu.au
Subject: Re: [RFC] Introduce __ARCH_WANT_SYS_SYSFS
Date: Wed, 23 Apr 2008 17:38:53 -0400 [thread overview]
Message-ID: <8bd0f97a0804231438u68118bc0t4abe8e85733b23f2@mail.gmail.com> (raw)
In-Reply-To: <480FA729.3000406@seznam.cz>
On Wed, Apr 23, 2008 at 5:16 PM, Michal Simek <monstr@seznam.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
next prev parent reply other threads:[~2008-04-23 21:39 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 12:13 Will Newton
2008-04-22 13:15 ` Arnd Bergmann
2008-04-23 21:16 ` Michal Simek
2008-04-23 21:38 ` Mike Frysinger [this message]
2008-04-24 11:11 ` microblaze syscall list Arnd Bergmann
2008-04-24 18:42 ` Michal Simek
2008-04-24 21:21 ` Arnd Bergmann
2008-04-25 9:36 ` [microblaze-uclinux] " John Williams
2008-04-25 10:06 ` Matthew Wilcox
2008-04-25 11:32 ` Geert Uytterhoeven
2008-04-27 2:04 ` John Williams
2008-04-27 15:52 ` Michal Simek
2008-04-27 16:50 ` Alan Cox
2008-04-27 20:15 ` Arnd Bergmann
2008-04-28 0:15 ` John Williams
2008-04-28 12:31 ` Arnd Bergmann
2008-05-01 19:17 ` Arnd Bergmann
2008-05-02 5:38 ` John Williams
2008-05-02 8:18 ` Michal Simek
2008-05-03 3:49 ` John Williams
2008-05-03 9:16 ` Arnd Bergmann
2008-05-03 15:56 ` Ulrich Drepper
2008-05-03 21:14 ` Arnd Bergmann
2008-05-05 1:09 ` John Williams
2008-05-05 14:08 ` Arnd Bergmann
2008-05-03 21:57 ` Arnd Bergmann
2008-05-04 9:12 ` Michal Simek
2008-05-04 19:37 ` Arnd Bergmann
2008-05-05 6:18 ` Michal Simek
2008-05-04 22:09 ` H. Peter Anvin
2008-05-04 22:54 ` Arnd Bergmann
2008-05-04 22:53 ` H. Peter Anvin
2008-05-06 8:33 ` Michal Simek
2008-04-24 20:51 ` Michal Simek
2008-04-24 21:37 ` Arnd Bergmann
2008-04-22 15:12 ` [RFC] Introduce __ARCH_WANT_SYS_SYSFS Randy Dunlap
2008-04-22 15:16 ` Will Newton
2008-04-22 15:24 ` Kyle McMartin
2008-04-22 15:34 ` Will Newton
2008-04-22 15:38 ` Kyle McMartin
2008-04-23 14:36 ` Will Newton
2008-04-23 14:59 ` Arnd Bergmann
2008-04-23 15:40 ` Kyle McMartin
2008-04-23 15:50 ` Will Newton
2008-04-23 16:05 ` Mike Frysinger
2008-04-23 17:59 ` Mike Frysinger
2008-04-24 9:18 ` Will Newton
2008-04-23 18:44 ` Sam Ravnborg
2008-04-24 14:51 ` Adrian Bunk
2008-04-22 15:21 ` Kyle McMartin
2008-04-22 15:38 ` Arnd Bergmann
2008-04-22 15:42 ` Kyle McMartin
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=8bd0f97a0804231438u68118bc0t4abe8e85733b23f2@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=arnd@arndb.de \
--cc=git@xilinx.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@seznam.cz \
--cc=will.newton@gmail.com \
/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®