From: Mark Anderson <manderso@lsil.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Red Hat 7.1 on Lion
Date: Wed, 31 Oct 2001 21:54:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805423@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805422@msgid-missing>
Sorry,
Step 3 should read this way:
3. change to the device, or use absolute path for the CDROM
(i.e. 'fs0:' NOT 'cd fs0:')
linux-ia64-request@linuxia64.org wrote:
>
> Send Linux-IA64 mailing list submissions to
> linux-ia64@linuxia64.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> or, via email, send a message with subject or body 'help' to
> linux-ia64-request@linuxia64.org
>
> You can reach the person managing the list at
> linux-ia64-admin@linuxia64.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linux-IA64 digest..."
>
> Today's Topics:
>
> 1. Red Hat 7.1 on Lion (Gururaj Ananthateerta)
> 2. LION hangs at init 0 (kernel 2.4.13 on top of SuSE 7.2a IA64 Dev.
> Ed.) (Verkist, Bruno)
> 3. Re: itc sync & clock_* (Jesse Barnes)
>
> --__--__--
>
> Message: 1
> Date: Tue, 30 Oct 2001 16:48:34 -0800
> From: Gururaj Ananthateerta <gururaj@cup.hp.com>
> Organization: Hewlett Packard
> Cc: "'linux-ia64@linuxia64.org'" <linux-ia64@linuxia64.org>
> Subject: [Linux-ia64] Red Hat 7.1 on Lion
>
> Is there any document which explains how to install linux on Lion.
> I am stuck in the EFI shell. I son't know how to install.
> Please help.
> Thanks
> Guru
>
> --__--__--
>
> Message: 2
> From: "Verkist, Bruno" <Bruno.Verkist@fujitsu-siemens.com>
> To: suse-ia64@suse.com
> Cc: linux-ia64 <linux-ia64@linuxia64.org>
> Date: Wed, 31 Oct 2001 09:35:36 +0100
> Subject: [Linux-ia64] LION hangs at init 0 (kernel 2.4.13 on top of SuSE 7.2a IA64 Dev.
> Ed.)
>
> Hi all,
>
> I have an Intel LION (8GB, 2x733MHz C0, BIOS 100, BMC 26) installed > with
> SuSE 7.2a IA64 Developers Edition (kernel 2.4.4). On top of it I > installed
> kernel 2.4.13 and the IA64 patch linux-2_4_13-ia64-011024_diff .
>
> Problem: When I reboot the machine with my new 2.4.13 kernel or switch > from
> runlevel 1 to 0 the system hangs while executing > /etc/rc.d/rc0.d/S20halt.
> The last messages I see on the screen are
>
> Sending all processes the TERM signal...
> Sending all processes the KILL signal...
> ...
> Týping <Ctrl-C>: blogd: Warning: the ioctl TIOCGDEV is not know by > the
> kernel
>
> After that I have to power cycle my LION (and repair my root file > system
> after reboot!).
>
> Bruno
>
> Bruno Verkist mailto:Bruno.Verkist@fujitsu-siemens.com
> FSC EP PS HE4, Paderborn Tel. +49 5251 8 15365
>
> --__--__--
>
> Message: 3
> Date: Wed, 31 Oct 2001 11:41:58 -0800
> From: Jesse Barnes <jbarnes@sgi.com>
> To: David Mosberger <davidm@hpl.hp.com>
> cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] itc sync & clock_*
>
> On Mon, 29 Oct 2001, David Mosberger wrote:
>
> > - if there is a driver for a fine-grained machine timer, it can
> > use it
>
> Right, and this should be some sort of generic interface that glibc can
> count on, right? I've been looking at the multimedia timer spec you
> mentioned for ideas about how to implement it.
>
> > Yup. The driver interface needs to allow direct user-level access to
> > the fine grained timer. Though I'd say the interface should be able
> > to accommodate hardware that can't map the timer into user space.
>
> Ok, I'll keep that in mind.
>
> Here's a patch against 2.4.13+ia64 to export the sal platform features to
> a directory in /proc. Please let me know if it's ok; I'll start working
> on the clock driver if it is.
>
> Thanks,
> Jesse
>
> diff -Naur --exclude=*~ --exclude=TAGS linux-2.4.13-ia64/arch/ia64/kernel/Makefile linux-2.4.13-ia64-salinfo/arch/ia64/kernel/Makefile
> --- linux-2.4.13-ia64/arch/ia64/kernel/Makefile Wed Oct 31 11:25:04 2001
> +++ linux-2.4.13-ia64-salinfo/arch/ia64/kernel/Makefile Wed Oct 31 11:27:31 2001
> @@ -15,7 +15,7 @@
>
> obj-y := acpi.o entry.o gate.o efi.o efi_stub.o ia64_ksyms.o irq.o irq_ia64.o irq_lsapic.o ivt.o \
> machvec.o pal.o process.o perfmon.o ptrace.o sal.o semaphore.o setup.o \
> - signal.o sys_ia64.o traps.o time.o unaligned.o unwind.o
> + signal.o sys_ia64.o traps.o time.o unaligned.o unwind.o salinfo.o
> obj-$(CONFIG_IA64_GENERIC) += iosapic.o
> obj-$(CONFIG_IA64_DIG) += iosapic.o
> obj-$(CONFIG_IA64_PALINFO) += palinfo.o
> diff -Naur --exclude=*~ --exclude=TAGS linux-2.4.13-ia64/arch/ia64/kernel/sal.c linux-2.4.13-ia64-salinfo/arch/ia64/kernel/sal.c
> --- linux-2.4.13-ia64/arch/ia64/kernel/sal.c Wed Oct 31 11:25:04 2001
> +++ linux-2.4.13-ia64-salinfo/arch/ia64/kernel/sal.c Wed Oct 31 11:29:00 2001
> @@ -19,6 +19,7 @@
> #include <asm/pal.h>
>
> spinlock_t sal_lock = SPIN_LOCK_UNLOCKED;
> +unsigned long sal_platform_features = 0;
>
> static struct {
> void *addr; /* function entry point */
> @@ -154,11 +155,13 @@
> struct ia64_sal_desc_platform_feature *pf = (void *) p;
> printk("SAL: Platform features ");
>
> - if (pf->feature_mask & (1 << 0))
> + if (pf->feature_mask & IA64_SAL_PLATFORM_FEATURE_BUS_LOCK) {
> printk("BusLock ");
> -
> - if (pf->feature_mask & (1 << 1)) {
> + sal_platform_features |= IA64_SAL_PLATFORM_FEATURE_BUS_LOCK;
> + }
> + if (pf->feature_mask & IA64_SAL_PLATFORM_FEATURE_IRQ_REDIR_HINT) {
> printk("IRQ_Redirection ");
> + sal_platform_features |= IA64_SAL_PLATFORM_FEATURE_IRQ_REDIR_HINT;
> #ifdef CONFIG_SMP
> if (no_int_routing)
> smp_int_redirect &= ~SMP_IRQ_REDIRECTION;
> @@ -166,14 +169,19 @@
> smp_int_redirect |= SMP_IRQ_REDIRECTION;
> #endif
> }
> - if (pf->feature_mask & (1 << 2)) {
> + if (pf->feature_mask & IA64_SAL_PLATFORM_FEATURE_IPI_REDIR_HINT) {
> printk("IPI_Redirection ");
> + sal_platform_features |= IA64_SAL_PLATFORM_FEATURE_IPI_REDIR_HINT;
> #ifdef CONFIG_SMP
> if (no_int_routing)
> smp_int_redirect &= ~SMP_IPI_REDIRECTION;
> else
> smp_int_redirect |= SMP_IPI_REDIRECTION;
> #endif
> + }
> + if (pf->feature_mask & IA64_SAL_PLATFORM_FEATURE_ITC_MAY_DRIFT) {
> + printk("ITC_may_drift ");
> + sal_platform_features |= IA64_SAL_PLATFORM_FEATURE_ITC_MAY_DRIFT;
> }
> printk("\n");
> break;
> diff -Naur --exclude=*~ --exclude=TAGS linux-2.4.13-ia64/arch/ia64/kernel/salinfo.c linux-2.4.13-ia64-salinfo/arch/ia64/kernel/salinfo.c
> --- linux-2.4.13-ia64/arch/ia64/kernel/salinfo.c Wed Dec 31 16:00:00 1969
> +++ linux-2.4.13-ia64-salinfo/arch/ia64/kernel/salinfo.c Wed Oct 31 11:36:35 2001
> @@ -0,0 +1,104 @@
> +/*
> + * salinfo.c
> + *
> + * Creates entries in /proc/sal for various system features.
> + *
> + * Copyright (c) 2001 Silicon Graphics, Inc. All rights reserved.
> + *
> + * 10/30/2001 jbarnes@sgi.com copied much of Stephane's palinfo
> + * code to create this file
> + */
> +
> +#include <linux/types.h>
> +#include <linux/proc_fs.h>
> +#include <linux/module.h>
> +
> +#include <asm/sal.h>
> +
> +MODULE_AUTHOR("Jesse Barnes <jbarnes@sgi.com>");
> +MODULE_DESCRIPTION("/proc interface to IA-64 SAL features");
> +
> +int salinfo_read(char *page, char **start, off_t off, int count, int *eof, void *data);
> +
> +typedef struct {
> + const char *name; /* name of the proc entry */
> + unsigned long feature; /* feature bit */
> + struct proc_dir_entry *entry; /* registered entry (removal) */
> +} salinfo_entry_t;
> +
> +/*
> + * List {name,feature} pairs for every entry in /proc/sal/<feature>
> + * that this module exports
> + */
> +static salinfo_entry_t salinfo_entries[]={
> + { "bus_lock", IA64_SAL_PLATFORM_FEATURE_BUS_LOCK, },
> + { "irq_redirection", IA64_SAL_PLATFORM_FEATURE_IRQ_REDIR_HINT, },
> + { "ipi_redirection", IA64_SAL_PLATFORM_FEATURE_IPI_REDIR_HINT, },
> + { "itc_may_drift", IA64_SAL_PLATFORM_FEATURE_ITC_MAY_DRIFT, },
> +};
> +
> +#define NR_SALINFO_ENTRIES (sizeof(salinfo_entries)/sizeof(salinfo_entry_t))
> +
> +/*
> + * One for each feature and one more for the directory entry...
> + */
> +static struct proc_dir_entry *salinfo_proc_entries[NR_SALINFO_ENTRIES + 1];
> +
> +static int __init
> +salinfo_init(void)
> +{
> + struct proc_dir_entry *salinfo_dir; /* /proc/sal dir entry */
> + struct proc_dir_entry **sdir = salinfo_proc_entries; /* keeps track of every entry */
> + int i;
> +
> + salinfo_dir = proc_mkdir("sal", NULL);
> +
> + for (i=0; i < NR_SALINFO_ENTRIES; i++) {
> + /* pass the feature bit in question as misc data */
> + *sdir++ = create_proc_read_entry (salinfo_entries[i].name, 0, salinfo_dir,
> + salinfo_read, (void *)salinfo_entries[i].feature);
> + }
> + *sdir++ = salinfo_dir;
> +
> + return 0;
> +}
> +
> +static void __exit
> +salinfo_exit(void)
> +{
> + int i = 0;
> +
> + for (i = 0; i < NR_SALINFO_ENTRIES ; i++) {
> + if (salinfo_proc_entries[i])
> + remove_proc_entry (salinfo_proc_entries[i]->name, NULL);
> + }
> +}
> +
> +/*
> + * 'data' contains an integer that corresponds to the feature we're
> + * testing
> + */
> +int
> +salinfo_read(char *page, char **start, off_t off, int count, int *eof, void *data)
> +{
> + int len = 0;
> +
> + MOD_INC_USE_COUNT;
> +
> + len = sprintf(page, (sal_platform_features & (unsigned long)data) ? "1" : "0");
> +
> + if (len <= off+count) *eof = 1;
> +
> + *start = page + off;
> + len -= off;
> +
> + if (len>count) len = count;
> + if (len<0) len = 0;
> +
> + MOD_DEC_USE_COUNT;
> +
> + return len;
> +}
> +
> +module_init(salinfo_init);
> +module_exit(salinfo_exit);
> diff -Naur --exclude=*~ --exclude=TAGS linux-2.4.13-ia64/include/asm-ia64/sal.h linux-2.4.13-ia64-salinfo/include/asm-ia64/sal.h
> --- linux-2.4.13-ia64/include/asm-ia64/sal.h Wed Oct 31 11:25:05 2001
> +++ linux-2.4.13-ia64-salinfo/include/asm-ia64/sal.h Wed Oct 31 11:32:32 2001
> @@ -149,6 +149,7 @@
> #define IA64_SAL_PLATFORM_FEATURE_BUS_LOCK (1 << 0)
> #define IA64_SAL_PLATFORM_FEATURE_IRQ_REDIR_HINT (1 << 1)
> #define IA64_SAL_PLATFORM_FEATURE_IPI_REDIR_HINT (1 << 2)
> +#define IA64_SAL_PLATFORM_FEATURE_ITC_MAY_DRIFT (1 << 3)
>
> typedef struct ia64_sal_desc_platform_feature {
> u8 type;
> @@ -775,5 +776,7 @@
> *scratch_buf_size_needed = isrv.v1;
> return isrv.status;
> }
> +
> +extern unsigned long sal_platform_features;
>
> #endif /* _ASM_IA64_PAL_H */
>
> --__--__--
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
> End of Linux-IA64 Digest
--
Mark Anderson
Software Test
Storage Standard Products
LSI Logic
Phone: 719-533-7507
Fax: 719-533-7430
E-mail: mark.anderson@lsil.com
Mailstop: AL-101
next prev parent reply other threads:[~2001-10-31 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 21:36 [Linux-ia64] Re: Red Hat 7.1 on Lion Mark Anderson
2001-10-31 21:54 ` Mark Anderson [this message]
2001-10-31 22:46 ` Gururaj Ananthateerta
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=marc-linux-ia64-105590698805423@msgid-missing \
--to=manderso@lsil.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox