public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: green <greenfreedom10@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: problem with n810 boot up
Date: Sat, 9 Jan 2010 11:43:44 -0600	[thread overview]
Message-ID: <201001091143.48472.luke@dashjr.org> (raw)
In-Reply-To: <20100109050338.GB9728@swansys>

On Friday 08 January 2010 11:03:38 pm green wrote:
> Luke-Jr wrote at 2010-01-05 17:46 -0600:
> > * N900 is supposedly mostly mainlined already, and supposedly Nokia will
> > actually finish the job with unlike N8x0; it also has nicer hardware,
> > even if you just ignore the cellular capabilities
> 
> You say "supposedly"; where do you get this information?  Is there a
>  mailing list or something...? 

IRC: #Maemo on FreeNode.

>  I would like to find out what works before  making a purchase. 
>  I made careless assumptions about Linux support when purchasing the N810.

Probably best to do a through study of the code, then. While things are 
supposedly better with the N900, things were supposedly good with the N810 
too, which was more or less advertised as being open source and running Linux 
even though neither will probably ever be true at this rate. Nokia has taught 
me not to trust such claims even when they have a large fan backing. :/

Luke

  reply	other threads:[~2010-01-09 17:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  7:52 [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810 Luke-Jr
2009-12-29  8:29 ` Kalle Valo
2009-12-29  8:46   ` Luke-Jr
2009-12-29  8:55     ` Kalle Valo
2009-12-29 12:51       ` Felipe Balbi
2009-12-29 21:05       ` Luke-Jr
2009-12-30  3:10         ` Luke-Jr
2009-12-30  7:17           ` Kalle Valo
2009-12-30  9:02             ` Luke-Jr
2009-12-30 12:04               ` Felipe Balbi
2009-12-30  7:14         ` Kalle Valo
2009-12-29 19:24 ` Tony Lindgren
2009-12-29 19:35   ` Felipe Balbi
2009-12-29 19:42     ` Tony Lindgren
2009-12-29 19:49       ` Felipe Balbi
2009-12-29 19:53         ` Tony Lindgren
2009-12-29 19:57           ` Felipe Balbi
2009-12-29 20:28   ` Luke-Jr
2009-12-29 20:35     ` Felipe Balbi
2010-01-05 23:24 ` problem with n810 boot up Francisco Alecrim
2010-01-05 23:46   ` Luke-Jr
2010-01-06  2:46     ` Francisco Alecrim
2010-01-06  3:07       ` Luke-Jr
2010-01-06 22:11         ` Francisco Alecrim
2010-01-06 22:45           ` Felipe Balbi
2010-01-06 23:02             ` Francisco Alecrim
2010-01-06 23:40               ` Luke-Jr
2010-01-06 23:59                 ` Francisco Alecrim
2010-01-07  0:10                   ` Luke-Jr
2010-01-07 15:25                     ` Francisco Alecrim
2010-01-07 15:40                       ` Luke-Jr
2010-01-07 16:55                         ` green
2010-01-09  2:56                           ` Luke-Jr
2010-01-09  4:59                             ` green
2010-01-07  0:33               ` Siarhei Siamashka
2010-01-07  2:04                 ` Francisco Alecrim
2010-01-09  5:03     ` green
2010-01-09 17:43       ` Luke-Jr [this message]
2010-01-09 23:53         ` green
     [not found]       ` <4B489CC5.5080700@gmail.com>
2010-01-09 23:35         ` green

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=201001091143.48472.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=greenfreedom10@gmail.com \
    --cc=linux-omap@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