public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 1/4] x86: base support for the TS-5500 platform
Date: Fri, 26 Aug 2011 20:00:40 -0400	[thread overview]
Message-ID: <20110826200040.2025eb0b@v0nbox> (raw)
In-Reply-To: <4E55836D.8030209@zytor.com>

On Wed, 24 Aug 2011 16:04:13 -0700,
"H. Peter Anvin" <hpa@zytor.com> wrote:

> On 08/24/2011 03:38 PM, Vivien Didelot wrote:
> > 
> > I agree with you. The platform does not provide many identification
> > points. We have specific hardware such as the CPU, Ethernet, Cardbus
> > and USB controllers; there is no DMI available; no PCI bridge
> > subvendor info, only the BIOS provides a 16-bit identification
> > call... We discussed that point in
> > https://lkml.org/lkml/2011/5/4/437 without success.
> > 
> > What would be the proper way in your opinion?
> > 
> > Vivien.
> 
> First of all, given that these clowns seem to be selling a product
> specifically targeting Linux support, they really need to be given a
> clue transfusion.  It is *NOT* acceptable to not provide DMI, and
> *NOT* acceptable not to set the subvendor information.
> 
> We should arguably push for them to fix that in their BIOSes, but that
> is as usual too little, too late.
> 
> Probably the best option we have is to look for some kind of magic
> string in their BIOS -- i.e. the classic way to detect things before
> DMI existed.
> 
> If not, you're going to have an explicit switch on the kernel command
> line, but that is an absolute last resort.
> 
> 	-hpa

Hi,

The initialization function is now reading the BIOS to find this magic
string, thanks for the tip. I've sent the updated version. The
corresponding thread is here: https://lkml.org/lkml/2011/8/26/425.

Regards,
Vivien.

  reply	other threads:[~2011-08-27  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 20:23 [PATCH 0/4] Support for the TS-5500 board Vivien Didelot
2011-08-24 20:23 ` [PATCH 1/4] x86: base support for the TS-5500 platform Vivien Didelot
2011-08-24 21:03   ` H. Peter Anvin
2011-08-24 22:08     ` Vivien Didelot
2011-08-24 22:10       ` H. Peter Anvin
2011-08-24 22:38         ` Vivien Didelot
2011-08-24 23:04           ` H. Peter Anvin
2011-08-27  0:00             ` Vivien Didelot [this message]
2011-08-24 20:23 ` [PATCH 2/4] x86: (TS-5500) add GPIO support Vivien Didelot
2011-08-24 20:23 ` [PATCH 3/4] x86: (TS-5500) add LED support Vivien Didelot
2011-08-24 20:23 ` [PATCH 4/4] x86: (TS-5500) add ADC support Vivien Didelot

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=20110826200040.2025eb0b@v0nbox \
    --to=vivien.didelot@savoirfairelinux.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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