From: bruno_vidal@hp.com
To: Lyonel Vincent <vincentl@ec-lyon.fr>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] enumerating devices from user space
Date: Fri, 14 Mar 2003 09:45:59 +0100 [thread overview]
Message-ID: <3E7196C7.8A35605F@hp.com> (raw)
In-Reply-To: 20030313134558.6cf9177c.vincentl@ec-lyon.fr
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Hi
I'll try to add an ioctls in my dump driver to print this list. It will
give a good starting point, isn't it ?
The other choice is to create a new modules that use my functions
in firmware.c. But keep in mind that it will usefull only for pa-risc.
I don't know if it is the best practice.
cheers.
Lyonel Vincent wrote:
> Hi Bruno,
>
> That sounds like what I was looking for (HW path + version information)!
> What do you think is the best approach?
>
> cheers,
> lv.
>
> On Thu, 13 Mar 2003 12:30:44 +0100
> bruno_vidal@hp.com wrote:
>
> > Hi guys.
> > While developping the dump modules, I had to find a way to retrieve
> > the hardware path of disk/hba. So I had to developpe a small hack
> > in the kernel/firmware.c in order to retrive the right hba.
> > But it is parisc dependant. Do you want I try to add an ioctl in my
> > dump modules in order to print in user space this informations ?
> > Example:
> >
> > size:1500160 nr_sects:3000320 start_sect:374784
> > hwpath: 0/0/1/1.15.0.0.
> > dump device opened: 0x813 with index: 0 at hpa: 0x900
> >
> > So my functions are able to print the hw path of each io modules.
> > Is it what you are looking for ?
> >
> > --
> > Vidal Bruno, (770-4271)
> > SSD-HA Team, HP-UX & LINUX Support
> > bruno_vidal@admin.france.hp.com
> >
> >
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
--
Vidal Bruno, (770-4271)
SSD-HA Team, HP-UX & LINUX Support
bruno_vidal@admin.france.hp.com
[-- Attachment #2: Card for --]
[-- Type: text/x-vcard, Size: 386 bytes --]
begin:vcard
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard
next prev parent reply other threads:[~2003-03-14 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 10:22 [parisc-linux] enumerating devices from user space Lyonel Vincent
2003-03-13 11:30 ` bruno_vidal
2003-03-13 12:45 ` Lyonel Vincent
2003-03-14 8:45 ` bruno_vidal [this message]
2003-03-14 12:33 ` Lyonel Vincent
2003-03-14 13:19 ` Matthew Wilcox
2003-03-14 14:05 ` Lyonel Vincent
2003-03-14 14:08 ` Matthew Wilcox
2003-03-14 17:29 ` Grant Grundler
2003-03-17 13:53 ` Lyonel Vincent
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 16:32 Lyonel Vincent
2003-03-12 16:48 ` Matthew Wilcox
2003-03-12 17:30 ` Lyonel Vincent
2003-03-12 20:50 ` Helge Deller
2003-03-12 22:36 ` Lyonel Vincent
2003-03-13 0:58 ` Matthew Wilcox
2003-03-13 8:23 ` Derek Engelhaupt
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=3E7196C7.8A35605F@hp.com \
--to=bruno_vidal@hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=vincentl@ec-lyon.fr \
/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