Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 2 days, 21 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 days, 17 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 1 hr ago - more...
|
2010-04-17
, 17:27
|
|
Posts: 235 |
Thanked: 163 times |
Joined on Dec 2008
@ Costa Rica
|
#22
|
Originally Posted by zehjotkah
Same here. I barely use my n810 since I bought my n900.
I can't code myself, but I have a N810 lying at home. How can I help?
Just let me know if testers are needed.
 |
|
2010-04-20
, 10:53
|
|
Posts: 13 |
Thanked: 8 times |
Joined on Aug 2009
@ Brazil - Piracicaba/SP
|
#23
|
Originally Posted by Termana
I Have a N800, would this kernel patch aply to my hardware? can i put it without fear?
n810 Rebased against 2.6.33.2 + MeeGo patches (all from here: http://repo.meego.com/MeeGo/devel/tr....2-7.3.src.rpm)
Includes zImage and patch.
http://bit.ly/aOzM0n
this 1.0 img is without graphics ui, did i get it right? is only 2megas? wow!
will an USB keyboard work since n800īs donīt get a slide keyboard one?
Since i should install it to run tests (if it is compatible to n800)
what shoud be the best way to provide feedback to you and install on it?
other things, here we are at maemo.org community, but meego.com is growning and have their own forum, wiki, etc.
If we start posting this subject here, can it be a way to the meego project see this iniciative more atached to their project and be more supportive?
__________________
--marshel--
brazilian n800 owner
curious by nature
--marshel--
brazilian n800 owner
curious by nature
|
|
2010-04-20
, 19:50
|
|
Posts: 207 |
Thanked: 31 times |
Joined on Apr 2008
|
#24
|
Originally Posted by Termana
I have some problem with this patch:
n810 Rebased against 2.6.33.2 + MeeGo patches (all from here: http://repo.meego.com/MeeGo/devel/tr....2-7.3.src.rpm)
Includes zImage and patch.
http://bit.ly/aOzM0n
1. Internel MMC doesn't recognized
2. Omap Soc sound driver module doesn't create:
Device Drivers --->
Sound card support --->
Advanced Linux Sound Architecture --->
ALSA for SoC audio support --->
<M> SoC Audio for the Texas Instruments OMAP chips
<M> SoC Audio support for Nokia N810
<M> Build all ASoC CODEC drivers
....
ERROR: "i2c_register_board_info" [sound/soc/omap/snd-soc-n810.ko] undefined!
3. What's with WiFi ?
Thank you
 |
|
2010-04-20
, 20:00
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#25
|
Originally Posted by Stskeeps
Instead of this hopping [in regards to N800/N810 OS] from Mer to Mer-whatver-version-2 to MeeGo maybe it would make sense to try to focus on sticking to one option and develop that.
So, this is a thread on starting work on a hardware adaptation for Nokia N8x0. (http://meego.com/developers/hardware-enabling-process). While I doubt we can be a first quality port due to need to upstream patches, we can try things and see how far we can get.
A starter is to grab the current kernel package from http://repo.meego.com/MeeGo/devel/tr....1-8.2.src.rpm , modify this with Termana and luke-jr's patches.
If we ask nicely, I think it should be possible to get repackaging done through my distmaster position so we can get the different firmwares, BME, etc provided through similar means (RPM repository) as tablets-dev.nokia.com does with the MeeGo on N900 things. So, we have a good start.
We can probably start with the chroot images (tar.gz) for N900 as they are fairly generic and the kickstart files.
__________________
.N810 experience: Since 6/2009
My Twenty Favorite OS2008 Applications:
AutoScan, Diablo5 Theme, Dialcentral, DragLock, EmelFM2, FlipClock, gPodder, Headphoned, Knots 2, Maemo Mapper, mPlayer, openNTPD, OpenSSH, Panucci, Personal Launcher, QuickNote, Seqretary, SlideLock, Telescope, YellowNotes
.N810 experience: Since 6/2009
My Twenty Favorite OS2008 Applications:
AutoScan, Diablo5 Theme, Dialcentral, DragLock, EmelFM2, FlipClock, gPodder, Headphoned, Knots 2, Maemo Mapper, mPlayer, openNTPD, OpenSSH, Panucci, Personal Launcher, QuickNote, Seqretary, SlideLock, Telescope, YellowNotes
Last edited by silvermountain; 2010-04-20 at 20:14.
| The Following User Says Thank You to silvermountain For This Useful Post: | ||
 |
|
2010-04-20
, 20:44
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#26
|
Originally Posted by silvermountain
My job is also to help start development of things in the community - hence some of the hopping. From a personal preference point of view, MeeGo on N8x0 has most future. But I don't know when MeeGo is day-to-day usable either.
Instead of this hopping [in regards to N800/N810 OS] from Mer to Mer-whatver-version-2 to MeeGo maybe it would make sense to try to focus on sticking to one option and develop that.
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
 |
|
2010-04-21
, 01:11
|
|
Posts: 32 |
Thanked: 74 times |
Joined on Sep 2009
@ South Australia
|
#27
|
Originally Posted by marshel
No, this patch will not work with an n800, only an n810. There is a link in my signature for a .34-rc3 kernel for n800 which was done by tmr - however the n800 .34-rc3 patch is not against the MeeGo kernel (obviously).
I Have a N800, would this kernel patch aply to my hardware? can i put it without fear?
Originally Posted by svs57
No, this is a known problem. The menelaus driver has the code for the internal MMC, however it doesn't get recognized. Upstream (linux-omap) don't know why this is either.
I have some problem with this patch:
1. Internel MMC doesn't recognized
Originally Posted by svs57
I have not tested anything outside of my base configuration (arch/arm/configs/n810_defconfig), including sound. There was someone that got sound working for the n810, I will be seeing if I can contact him, if not I will try and get it working myself.
2. Omap Soc sound driver module doesn't create:
Originally Posted by svs57
You need to include the p45spi driver into the config. If you look at the .33.1 kernel thread linked in my signature some people have got it working, I have not done any testing on this either and is not included in the base configuration.
3. What's with WiFi ?
I will be performing some testing on these components and making a new patch file soon.
__________________
Follow me @Termana on Twitter
Follow me @Termana on Twitter
|
|
2010-04-21
, 13:56
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#28
|
Originally Posted by Stskeeps
Does your job also include finishing a project because I haven't seen much of that?
My job is also to help start development of things in the community - hence some of the hopping. From a personal preference point of view, MeeGo on N8x0 has most future. But I don't know when MeeGo is day-to-day usable either.
Along those lines, since you say that MeeGo in your personal opinion has most future does that mean that Nokia is supporting Mer and if not then why is Mer being worked on if MeeGo in your opinion is a more plausible OS option?
I'm sorry to sound 'bitter' but honestly the lack of focus ('Mer for N8xx', 'No wait, we're also doing Mer for N900', 'No wait Mer is dead now it's Mer2 that will come', 'Oh wait. no MeeGo on N8xx is better') is indeed rather tiring and has become one huge disappointment.
If your job, as you mention above, is to start development of things in the community I think you've done that. But if you going forward expect people to beta test, etc you might also want to think about sticking to a project.
__________________
.N810 experience: Since 6/2009
My Twenty Favorite OS2008 Applications:
AutoScan, Diablo5 Theme, Dialcentral, DragLock, EmelFM2, FlipClock, gPodder, Headphoned, Knots 2, Maemo Mapper, mPlayer, openNTPD, OpenSSH, Panucci, Personal Launcher, QuickNote, Seqretary, SlideLock, Telescope, YellowNotes
.N810 experience: Since 6/2009
My Twenty Favorite OS2008 Applications:
AutoScan, Diablo5 Theme, Dialcentral, DragLock, EmelFM2, FlipClock, gPodder, Headphoned, Knots 2, Maemo Mapper, mPlayer, openNTPD, OpenSSH, Panucci, Personal Launcher, QuickNote, Seqretary, SlideLock, Telescope, YellowNotes
 |
|
2010-04-21
, 14:55
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#29
|
Originally Posted by silvermountain
While I understand the point you're making here, you have to understand that there has been a lot of churn and change that has forced plans (not just Mer, everywhere) to change in very big ways over time. MeeGo's very existence changes a lot of things, at least as far as I'm concerned, because it addresses a lot of the same problems Mer set out to accomplish (such as easier porting to devices).
Does your job also include finishing a project because I haven't seen much of that?
Along those lines, since you say that MeeGo in your personal opinion has most future does that mean that Nokia is supporting Mer and if not then why is Mer being worked on if MeeGo in your opinion is a more plausible OS option?
I'm sorry to sound 'bitter' but honestly the lack of focus ('Mer for N8xx', 'No wait, we're also doing Mer for N900', 'No wait Mer is dead now it's Mer2 that will come', 'Oh wait. no MeeGo on N8xx is better') is indeed rather tiring and has become one huge disappointment.
If your job, as you mention above, is to start development of things in the community I think you've done that. But if you going forward expect people to beta test, etc you might also want to think about sticking to a project.
And it's not just limited to new tech/etc introducing changes, just *doing* some of this stuff teaches lessons that force plans and other things to change in order to remain relevant and realistic. While I wasn't actively around for the earlier days of Mer, I've enjoyed watching it - and the people involved with it - evolve to meet the challenges of the growing requirements.
So no. It hasn't -yet- produced something of shipping quality, but I don't think there's been a better road to go along to learn how to get things done, and I remain hopeful that MeeGo will help to produce a stable and productive base platform for use on a wide variety of devices, including older NITs.
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
| The Following 3 Users Say Thank You to w00t For This Useful Post: | ||
|
|
2010-04-21
, 18:54
|
|
Posts: 119 |
Thanked: 412 times |
Joined on Aug 2008
|
#30
|
Originally Posted by silvermountain
Sometimes you have to look at the amount of support a project gets and say "not enough people care".
Does your job also include finishing a project because I haven't seen much of that?
Along those lines, since you say that MeeGo in your personal opinion has most future does that mean that Nokia is supporting Mer and if not then why is Mer being worked on if MeeGo in your opinion is a more plausible OS option?
I'm sorry to sound 'bitter' but honestly the lack of focus ('Mer for N8xx', 'No wait, we're also doing Mer for N900', 'No wait Mer is dead now it's Mer2 that will come', 'Oh wait. no MeeGo on N8xx is better') is indeed rather tiring and has become one huge disappointment.
If your job, as you mention above, is to start development of things in the community I think you've done that. But if you going forward expect people to beta test, etc you might also want to think about sticking to a project.
At least, not enough care enough to spend time making it happen.
As an example: How much time have you personally put into Mer silvermountain? Either development, docs, supporting others .. that kind of thing?
Probably not a lot - and that's fine, it's a volunteer thing
However, if not enough people volunteer then.... it doesn't happen.
It turns out that Merm as originally conceivedm was too hard for just a few core devs to deliver and, IMHO, the maemo community didn't engage enough.
Oh, and if you find it disappointing that it wasn't delivered then how disappointing do you think it is when you spend literally months of your life non-stop, 12+hours a day, 7 days a week working on a project and people typically say "Isn't it ready yet? Oh, I can't code, sorry." (I do sometimes wonder if it will come as a surprise to many of those people to find that coders learn to code by doing research and working at it!)
Anyhow...
Meego, by contrast, is much more open and reduces the effort needed to get the N8x0 up and running. There should be a reference UI too - lots of things to make it easier.
| The Following 6 Users Say Thank You to lbt For This Useful Post: | ||
 |
| Tags |
| hardware adaptation, meego |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 22:13.
Includes zImage and patch.
http://bit.ly/aOzM0n
Follow me @Termana on Twitter