Ticket #133 (closed enhancement: fixed)

Opened 6 months ago

Last modified 12 days ago

update n8x0 to diablo kernel and fix up kernel preferred versions

Reported by: trickie Owned by:
Priority: normal Milestone:
Component: Build System Version:
Keywords: Cc:

Description

This updates the nokia800 machines (n8x0's) to the diablo kernel, and changes the preferred kernel version setup.

Now each conf/machine/* conf file sets the PREFERRED_PROVIDER_virtual/kernel and any per machine version is specified in conf/distro/mamona.conf.

I set my MAMONA_MACHINE to nokia770, nokia800 and omap3430sdp and each now builds the specified provider of virtual/kernel with the version set in mamona.conf. I do not know if there are other machines that you guys use that need to this set.

I also flashed and booted the diablo kernel I built on my n800, worked fine for me.

Attachments

mamona-kernel-stuff.patch (38.8 kB) - added by trickie 6 months ago.
diablo kernel and updated preferred providers/versions

Change History

Changed 6 months ago by trickie

diablo kernel and updated preferred providers/versions

follow-up: ↓ 2   Changed 6 months ago by rsalveti

LGTM, I was only thinking about the problem of compiling the kernel using another toolchain, mostly because of the proprietary drivers that will not work if you don't use the same toolchain.

I think we have 2 options here:

  1. use this recipe and compile the kernel with another toolchain and forgetting about the proprietary drivers (I guess the wireless driver is one example);
  2. modify the recipe to use the same toolchain that nokia used to build the diablo's kernel (if we have access to it), so you could build a new kernel with the possibility to load all proprietary modules it has.

What do you think about it?

in reply to: ↑ 1   Changed 6 months ago by trickie

Replying to rsalveti:

Hi

LGTM, I was only thinking about the problem of compiling the kernel using another toolchain, mostly because of the proprietary drivers that will not work if you don't use the same toolchain. I think we have 2 options here: 1. use this recipe and compile the kernel with another toolchain and forgetting about the proprietary drivers (I guess the wireless driver is one example); 1. modify the recipe to use the same toolchain that nokia used to build the diablo's kernel (if we have access to it), so you could build a new kernel with the possibility to load all proprietary modules it has. What do you think about it?

Well atm I am running a kernel I built with this recipe for my n800, and I have wifi etc working ok, but i guess i see the issue, where that may not work in the future.

I also play around with later linux-omap kernels, and i lose wifi doing that anyway, so that doesn't bother me.

But I will see if I have access to the toolchain nokia uses and if so, we may as well use that to keep functionality in the nokia supplied kernel sources.

What do you guys think?

  Changed 6 months ago by rsalveti

As we don't compile a new kernel when installing mamona at a new machine, I guess that there's no big issue of letting the user compile it with a different toolchain, the user knows that he's building a custom kernel.

I guess we can apply this version and if we face this problem in the future we can fix the build to use another toolchain.

Just need to test your patch and we can apply it :-)

  Changed 12 days ago by sunrise

This works ok for me.. but It probably needs feedback. openbossa Air Jordan
Note: See TracTickets for help on using tickets.