mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Miguel Ojeda <maxextreme@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: crash on CONFIG_CFAG12864B=y in 2.6.20-rc3-mm1
Date: Thu, 01 Feb 2007 09:20:33 -0800	[thread overview]
Message-ID: <1170350433.9781.200.camel@imap.mvista.com> (raw)
In-Reply-To: <653402b90702010913g3d91b190ud4faa2bcce3251b@mail.gmail.com>

On Thu, 2007-02-01 at 18:13 +0100, Miguel Ojeda wrote:

> >
> >
> 
> Well, I use the word "module" for both cases: When I modprobe
> cfag12864b, if ks0108 fails, it doesn't get linked. So I thought the
> same happen for built-in drivers (in other words, I didn't think
> cfag12864b would be linked if ks0108 failed).
> 
> So I'm waiting until someone tell me what is the right way to avoid
> drivers like cfag12864b been inited if their dependencies failed.
> 
> Anyway, thanks for discovering the bug (I wouldn't have discovered it
> as my motherboard has parallel port ;).

I have a parallel port, but I don't have the cfag12864b or ks0108 .. I
think the simplest way to fix it would be to add a flag to ks0108 that
signals successful initialization , then force cfag12864b to check for
that ..

I found this by booting a make allyesconfig kernel ..

Daniel


  reply	other threads:[~2007-02-01 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 16:55 Daniel Walker
2007-02-01 13:49 ` Miguel Ojeda
2007-02-01 15:16   ` Miguel Ojeda
2007-02-01 15:16     ` Daniel Walker
2007-02-01 17:13       ` Miguel Ojeda
2007-02-01 17:20         ` Daniel Walker [this message]
2007-02-01 17:39           ` Miguel Ojeda
2007-02-01 17:55             ` Daniel Walker
2007-02-01 18:17               ` Miguel Ojeda
2007-02-04 16:12 Miguel Ojeda

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=1170350433.9781.200.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@gmail.com \
    /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
all inboxes | Powered by JetHome®