public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Juha Yrjola <juha.yrjola@solidboot.com>
To: Lauri Leukkunen <lauri.leukkunen@nokia.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
	Tony Lindgren <tony@atomide.com>,
	"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
	"Tereshonkov Roman (Nokia-D/Helsinki)"
	<roman.tereshonkov@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3: SDTI: Prevent access to sdti writing if module is not initialized.
Date: Mon, 2 Mar 2009 13:31:12 +0200	[thread overview]
Message-ID: <20090302113112.GA15810@mail.solidboot.com> (raw)
In-Reply-To: <20090302082750.GC24691@pure.research.nokia.com>

On Mon, Mar 02, 2009 at 10:27:50AM +0200, Lauri Leukkunen wrote:

> > STI console is enabled based on runtime decisions by the bootloader. The
> > kernel command line is unusable for us, because there is no way to append to
> > the line. We don't want to remove the possibility how having the user
> > create a custom kernel with a custom command line.
> 
> *I* don't have a problem with having the bootloader always define the
> cmdline, you are the one against it :)

If we did that, how would the kernel flashing process go?

Cheers,
Juha

  reply	other threads:[~2009-03-02 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 11:39 [PATCH] OMAP3: SDTI: Prevent access to sdti writing if module is not initialized Roman Tereshonkov
2009-02-16 11:33 ` Felipe Balbi
2009-02-27 18:35   ` Tony Lindgren
2009-02-27 19:00     ` Felipe Balbi
2009-02-28 10:08       ` Juha Yrjola
2009-03-02  8:27         ` Lauri Leukkunen
2009-03-02 11:31           ` Juha Yrjola [this message]
2009-03-02 12:15             ` Lauri Leukkunen

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=20090302113112.GA15810@mail.solidboot.com \
    --to=juha.yrjola@solidboot.com \
    --cc=felipe.balbi@nokia.com \
    --cc=lauri.leukkunen@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --cc=roman.tereshonkov@nokia.com \
    --cc=tony@atomide.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