From: Kirill Tkhai <tkhai@yandex.ru>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.10.10-rt7
Date: Fri, 04 Oct 2013 16:57:33 +0400 [thread overview]
Message-ID: <448111380891453@web20m.yandex.ru> (raw)
In-Reply-To: <20131004122703.GC19953@linutronix.de>
04.10.2013, 16:27, "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>:
> * Kirill Tkhai | 2013-08-30 21:16:08 [+0400]:
>
>> sparc does not have CONFIG_EARLY_PRINTK option.
>>
>> So early-printk-consolidate.patch breaks compilation:
>>
>> arch/sparc/built-in.o: In function `setup_arch':
>> (.init.text+0x15e4): undefined reference to `early_console'
>> arch/sparc/built-in.o: In function `setup_arch':
>> (.init.text+0x15ec): undefined reference to `early_console'
>
> that is true and I applied that patch, thanks.
> However with this alone you do not have a working RT on Sparc because
> you can't select "Fully Preemptible Kernel (RT)" only the "basic" system
> is available.
Yes, I now. I added IRQ_FORCED_THREADING to Kconfig. My hardware
requires additional changes at arch/sparc and it's in a process of porting
on 3.10 so I can't say if everything works on sparc or not yet.
The other required fix to make sparc64 compilable is deletion of rwsem leftovers.
I sent it to mainline sparc:
https://git.kernel.org/cgit/linux/kernel/git/davem/sparc.git/commit/arch/sparc?id=61d9b9355b0d427bd1e732bd54628ff9103e496f
It seems it's resonable to add it to the patch too.
next prev parent reply other threads:[~2013-10-04 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 18:42 [ANNOUNCE] 3.10.10-rt7 Sebastian Andrzej Siewior
2013-08-30 10:32 ` Bernhard Schiffner
2013-10-04 18:34 ` Sebastian Andrzej Siewior
2013-08-30 17:16 ` Kirill Tkhai
2013-10-04 12:27 ` Sebastian Andrzej Siewior
2013-10-04 12:57 ` Kirill Tkhai [this message]
2013-10-04 13:05 ` Sebastian Andrzej Siewior
2013-10-04 13:11 ` Kirill Tkhai
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=448111380891453@web20m.yandex.ru \
--to=tkhai@yandex.ru \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.