public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cleanup kbuild for aic7xxx
Date: Fri, 22 Jun 2001 23:41:28 -0600	[thread overview]
Message-ID: <3B342C08.941D5F46@idcomm.com> (raw)
In-Reply-To: <200106230504.f5N54AU84337@aslan.scsiguy.com>

"Justin T. Gibbs" wrote:
> 
> >> >Users don't have to manually select "rebuild firmware".  They can
> >> >rely on the generated files already in the aic7xxx directory.  This
> >> >is why the option defaults to off.
> >
> >For the SGI patched kernels based on either 2.4.5 or 2.4.6-pre1, I have
> >had to manually select this for a 7892 controller. Without manually
> >selecting it, it guarantees boot failure. I don't know if this is due to
> >the SGI modifications or not. The real problem I found is that during
> >boot failure, there was no meaningful debug message.
> 
> I don't know why your kernel source is out of sync.  I will have to
> go pull down the 2.4.5 and 2.4.6 trees and see if some portion of
> my patches never made it into those trees.  It also looks like the
> comment section for this option didn't make it into my 2.4.4 and above
> patches.  I'll correct this on this on Monday.  Here's the relevent
> info.  Do you have any comments on what would make it more useful?
> 
> +Build Adapter Firmware with Kernel Build
> +CONFIG_AIC7XXX_BUILD_FIRMWARE
> +  This option should only be enabled if you are modifying the
> +  firmware source to the aic7xxx driver and wish to have the
> +  generated firmware include files updated during a normal
> +  kernel build.  The assmebler for the firmware requires
> +  lex and yacc or their equivalents, as well as the db v1
> +  library.  You may have to install additional packages or
> +  modify the assmebler make file or the files it includes
> +  if your build environment is different than that of the
> +  author.

I would add a note to try without it at first, but if bootup starts
normally, then hangs in what seems like a controller or filesystem
failure of a scsi drive, try to enable the option.

(this would give some hint about debugging an aic7xxx failure,
regardless of error messages)

D. Stimits, stimits@idcomm.com

> 
> >Missing firmware rebuild is fatal for my system, SMP x86 with integrated
> >7892. Messages and config menu information is inadequate, it requires a
> >bit of pounding the head on the wall to figure it out.
> 
> It is hard to make the kernel driver give a reasonable message for every
> possible error that running with incompatible components may cause.
> 
> --
> Justin

      reply	other threads:[~2001-06-23  5:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 17:52 Cleanup kbuild for aic7xxx Keith Owens
2001-06-22 19:39 ` Justin T. Gibbs
2001-06-23  0:50   ` Keith Owens
2001-06-23  1:20     ` J . A . Magallon
2001-06-23  1:54       ` Keith Owens
2001-06-23  2:38       ` Justin T. Gibbs
2001-06-23  4:19       ` D. Stimits
2001-06-23  1:32     ` David Ford
2001-06-23  2:46       ` Justin T. Gibbs
2001-06-23  2:57         ` David Ford
2001-06-23  3:07           ` Justin T. Gibbs
2001-06-23  3:57             ` David Ford
2001-06-23  5:10               ` Justin T. Gibbs
2001-06-23  4:41             ` David Ford
2001-06-23  5:11               ` Justin T. Gibbs
2001-06-23  5:58                 ` [working] Re: Cleanup kbuild for aic7xxx (attn: Alan & Doug) David Ford
2001-06-23  4:58             ` Cleanup kbuild for aic7xxx David Ford
2001-06-23  2:34     ` Justin T. Gibbs
2001-06-23  5:22       ` Keith Owens
2001-06-25 18:22         ` Justin T. Gibbs
2001-06-26  2:34           ` Keith Owens
2001-06-26  4:27             ` Justin T. Gibbs
2001-06-23  4:17     ` D. Stimits
2001-06-23  4:54       ` Keith Owens
2001-06-23  5:14         ` Justin T. Gibbs
2001-06-23  5:34           ` Keith Owens
2001-06-23  5:04       ` Justin T. Gibbs
2001-06-23  5:41         ` D. Stimits [this message]

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=3B342C08.941D5F46@idcomm.com \
    --to=stimits@idcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox