ep. quite simply, it looks out of place. unless
there's something unusual happening here, i would think that it's not
the romfs target's responsibility to do that kernel step -- that
should be left for the final initramfs image creation step, no?
rday
--
==
would it be possible for someone to add a kernel-like "make help"
target to dump at least the most commonly-used targets to the
top-level Makefile? not sure about anyone else, but *i'd* find that
handy.
rday
--
======
irrelevant right now.
http://www.crashcourse.ca/wiki/index.php/Writing_your_first_kernel_module
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lec
Using 32768
> > */
> > -. = ALIGN(4096);
> > +. = ALIGN(8192); /* MUST be 8192, the THREAD_SIZE */
> > *(.data.init_task)
> > *(.data)
is the macro THREAD_SIZE not defined so that it can be used instead of
hardcoding the value 8192?
rday
==========
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
at's what it's
based on. but that's just being picky.
rday
--
============
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
_
heir* cloned
repo.
and since i'm not a git expert, i'm open to advice on the best way to
do that. and thoughts on whether any of this makes sense.
comments? have i forgotten anything? is this the normal way that
someone creates a git repository to support a processor port?
rday
mory()
once i figure out what to do about those, i might actually have a
kernel.
--
============
Robert P. J. Day
Linux Consulting, Traini
ios2nommu/kernel/dma.c.
any thoughts on what those two routines should look like for nios2?
thanks.
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario,
rday
--
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcour
addr_t dma_address;
unsigned int length;
};
#define ISA_DMA_THRESHOLD (0x)
#define sg_dma_address(sg) (virt_to_bus((sg)->dma_address))
#define sg_dma_len(sg) ((sg)->length)
#endif /* __ASM_NIOS2_SCATTERLIST_H */
=
On Sat, 27 Oct 2007, Atle Nissestad wrote:
> Robert P. J. Day wrote:
> > as a quick followup to this earlier post of mine:
> >
> > http://mailman.uclinux.org/pipermail/uclinux-dev/2007-October/044410.html
> >
> > can anyone verify one way or the other whether a
ght affect other architectures as well if they've hard-coded
references to "sg->page" anywhere.
--
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
default y
i'm not a DMA wizard, but i can say that adding the above cures the
build problem. i'm just not sure if it's the *right* solution, that's
all. thanks.
rday
--
================
Robert P. J. Day
Linux
e sooner, the better, which is why i'm posting so
frequently. no sense dragging this out, but if folks think i'm
abusing the mandate of the mailing list, i'll respect that and take
the discussion elsewhere.
rday
--
===
ure out how to fix
build errors, even when i don't understand what's going on in the
underlying code. you'd be better off (at least for now) hoping
someone else on this list knows more about the i2c-gpio stuff than i
do.
rday
--
====
a different solution to the above?
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
___
uClinux-dev m
DMA issues. more later.
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
___
uClinux-dev mailing lis
On Fri, 26 Oct 2007, David McCullough wrote:
>
> Jivin Robert P. J. Day lays it down ...
> >
> > really? that's just weird, having the CVS repo lagging behind
> > tarball snapshots. what's the rationale for *that*? it certainly
> > flies in the face of s
e for nios2
contains:
# CONFIG_BLK_DEV_INITRD is not set
so what's the proper solution? just remove the #ifdef and #endif
from around that header file include? that seems like the obvious
solution, but i'd like some corroboration on that.
rday
--
=======
reference deleted
i'm assuming that that should be sufficient. it did, in fact,
resolve the ic2 gpio circular dependency problem. whether it works
properly later is still to be determined.
rday
--
Robert
standard kernel stuff is now sufficient?
rday
--
====
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crash
ast two macros, which were moved here from
the header file include/asm-nios2nommu/pci.h, to be consistent with
how all the other arches do it.
does that look remotely sane? i'm about to test it.
rday
--
================
Robert
On Thu, 25 Oct 2007, David McCullough wrote:
> Jivin Robert P. J. Day lays it down ...
> >
> > sorry to pollute the list this much but i forgot to mention one
> > more thing about my current uclinux nios2 patchset.
> >
> > i'm test building this kernel
eft it for now.
does all that make sense? i'll be back in a day or so to pick up
where i left off.
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pe
kernel (not
all of uclinux) with what i have dies at the asm/scatterlist.h
incompatibility, but you mentioned that you already know how to deal
with that so i'll leave it with you to play with that until i get
back.
rday
--
===============
r
i'll just fake it and make it look vaguely like the rest and take my
chances.
rday
--
============
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterlo
thanks.
rday
--
============
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://
read_info +
> stack_offset);
> + childregs = (struct pt_regs *) ((unsigned long) p->stack +
> stack_offset);
> p->thread.kregs = childregs;
>
> *childregs = *regs;
ok, i'll deal with that as well when i get back to my system, thanks.
rday
--
==
... uh oh ...
so the obvious question is, what *should* that DEFINE look like? is
it actually wanting to refer to thread_info itself? or to the stack?
rday
--
================
Robert P. J. Day
Linux Consulting, Training and Annoying K
when it already exists, which is apparently what's causing the
circular definition error.
thoughts? is there something subtle here i'm not appreciating?
rday
--
============
Robert P. J. Day
Linux Consulting, Training
On Wed, 24 Oct 2007, Michael Schnell wrote:
> Robert P. J. Day wrote:
> > given that there are other forums to discuss the nios2 soft-core
> > processor, is this still an appropriate place to ask about
> > building a kernel for the nios2 using uclinux? thanks
> I d
given that there are other forums to discuss the nios2 soft-core
processor, is this still an appropriate place to ask about building a
kernel for the nios2 using uclinux? thanks.
rday
--
Robert P. J. Day
Linux
33 matches
Mail list logo
