From: Greg KH <greg@kroah.com>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Fri, 27 Sep 2002 15:33:39 -0700 [thread overview]
Message-ID: <20020927223338.GX12909@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209271606001.16331-100000@humbolt.us.dell.com>
Looks nice, just a few minor comments:
> $ cat int13_dev80/host_bus
> PCI 02:01.0 channel: 0
> $ cat int13_dev80/interface
> SCSI id: 0 lun: 0
> $ cat int13_dev80/info
> 80 30 01 00 .0..
> 1e 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 3a b9 8b 08 00 00 00 00 00 02 ff ff ff ff be dd :...............
> 2c 00 00 00 50 43 49 00 53 43 53 49 00 00 00 00 ,...PCI.SCSI....
> 02 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 28 .........(
> version: 3.0
> Extensions:
> Fixed disk access
> Info Flags:
> dma_boundry_error_transparent
> write_verify
> num_default_cylinders: 0
> num_default_heads: 0
> sectors_per_track: 0
> number_of_sectors: 88bb93a
> PCI 02:01.0 channel: 0
> SCSI id: 0 lun: 0
>
> Warning: Spec violation. Key should be 0xBEDD, is 0xDDBE
>
Don't you already get the PCI and SCSI lines in the info file, from the
host_bus and interface files?
And that's a nice way to export binary data through a text file :)
Any way to split out the fields as individual files (version,
extensions, info_flags, num_default_cylinders, and so on)?
> @@ -981,3 +981,13 @@
> absence of features.
>
> For more information take a look at Documentation/swsusp.txt.
> +
> +CONFIG_EDD
> + Say Y or M here if you want to enable BIOS Enhanced Disk Device
> + Services real mode BIOS calls to determine which disk
> + BIOS tries boot from. This feature creates a /proc/edd directory
> + and files for each BIOS device detected.
You should fix up this wording as you aren't doing anything in the /proc
fs anymore :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-09-27 22:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt Domsch
2002-09-27 22:33 ` Greg KH [this message]
2002-09-29 16:11 ` Dave Jones
2002-09-29 16:18 ` Zwane Mwaikambo
2002-09-29 16:44 ` Alan Cox
2002-09-29 18:20 ` Kai Germaschewski
2002-09-29 18:27 ` Russell King
2002-09-29 18:52 ` Dave Jones
2002-10-01 1:55 ` Patrick Mochel
2002-10-01 3:37 Matt_Domsch
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 4:32 Matt_Domsch
2002-09-11 19:09 Matt_Domsch
2002-09-12 18:00 ` Patrick Mochel
2002-09-12 18:48 ` Matt Domsch
2002-09-10 22:43 Matt_Domsch
2002-09-09 1:17 Matt_Domsch
2002-09-04 0:54 Matt_Domsch
2002-09-04 1:09 ` Daniel Phillips
2002-09-04 4:17 ` Greg KH
2002-09-08 0:39 ` Patrick Mochel
2002-09-03 22:05 Matt Domsch
2002-09-03 23:29 ` Daniel Phillips
2002-09-04 4:35 ` Andre Hedrick
2002-09-04 16:02 ` Matt Domsch
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=20020927223338.GX12909@kroah.com \
--to=greg@kroah.com \
--cc=Matt_Domsch@Dell.com \
--cc=linux-kernel@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.