From: Jiri Slaby <jslaby@suse.cz>
To: Tony Luck <tony.luck@intel.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
fenghua.yu@intel.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] IA64: hpsim, fix SAL handling in fw-emu
Date: Fri, 24 Feb 2012 23:44:37 +0100 [thread overview]
Message-ID: <4F4812D5.7060606@suse.cz> (raw)
In-Reply-To: <CA+8MBbKtQZkp0RzsP366PgzdN2jvX73njFr1avSoE_CFDv=jNg@mail.gmail.com>
On 02/24/2012 11:32 PM, Tony Luck wrote:
> Are these four patches the only things needed to get the kernel
> running on the simulator? I've been building sim_defconfig as
> part of my regular "did things break" cycle. But I haven't tried to
> boot in well over five years.
Yes, it works fine for me. I'm using busybox as userspace. From SLES 11
SP2. I was using it to test tty patches applied to simserial.
My .config differs from sim_defconfig though. I didn't know there is a
defconfig for HP simulator. So I configured the kernel from scratch with
help of menuconfig.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-02-24 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 11:10 [PATCH 1/4] IA64: hpsim, fix SAL handling in fw-emu Jiri Slaby
2012-02-24 11:10 ` [PATCH 2/4] IA64: simserial, include some headers Jiri Slaby
2012-02-24 11:10 ` [PATCH 3/4] IA64: hpsim, initialize chip for assigned irqs Jiri Slaby
2012-02-24 11:10 ` [PATCH 4/4] IA64: simserial, bail out when request_irq fails Jiri Slaby
2012-02-24 22:32 ` [PATCH 1/4] IA64: hpsim, fix SAL handling in fw-emu Tony Luck
2012-02-24 22:44 ` Jiri Slaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-08 19:50 [PATCH 00/68] TTY buffer in tty_port -- prep no. 1 Greg KH
2012-03-08 20:01 ` [PATCH 1/4] [IA64] hpsim, fix SAL handling in fw-emu Jiri Slaby
2012-03-08 20:29 ` Greg KH
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=4F4812D5.7060606@suse.cz \
--to=jslaby@suse.cz \
--cc=fenghua.yu@intel.com \
--cc=jirislaby@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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