Messages in this thread | | | Date | Tue, 22 May 2007 20:28:28 -0400 | From | "Mike Frysinger" <> | Subject | Re: [PATCH 00/32] Blackfin update for 2.6.22-rc2 |
| |
On 5/21/07, Paul Mundt <lethal@linux-sh.org> wrote: > On Mon, May 21, 2007 at 10:35:08AM -0400, Robin Getz wrote: > > On Mon 21 May 2007 06:09, Bryan Wu pondered: > > > Lots of update for 2.6.22-rc2 and tested on STAMP537 board. > > > > > > > One of the things I noticed when trying out 2.6.22-rc1, on blackfin was: > > > > CALL scripts/checksyscalls.sh > [snip syscalls] > > > > since there is noMMU, are we better: > > - putting stubs (return ENOSYS - give runtime errors), or > > - just ignore the errors - and give compile errors? (Is there any way to put > > something into the syscall table, as not to get the warnings?) > > No, you'd be better of figuring out which ones you can support and which > ones you have to -ENOSYS. CONFIG_MMU=n is not a "get out of syscalls > free" card. Many of these have no dependency on CONFIG_MMU, anyways.
when you say -ENOSYS, do you mean we need sys_foo() that simply does return -ENOSYS or do we just let the default syscall code go "__NR_foo is not registered, return -ENOSYS" -mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |