Layout of Freescale kernel git repository

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Layout of Freescale kernel git repository

863 Views
PhilEndecott
Contributor II
Dear Experts, I am trying to understand the layout of the Freescale git kernel repository at http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git . I'm not a git expert. I had hoped that by cloning that URL I'd get the most up-to-date i.MX kernel source. In fact, I end up with something that doesn't work because things are missing, including the early serial console (mxc_uart_early.c) and the AHCI (SATA) bus glue (ahci_sata.c). On the other hand, it seems that different "heads" in that repository, e.g. http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=tree;h=refs/heads/imx_2.6.38_11.09.01;... do include these things (though I've not yet tried to build one). But that's (presumably) 2.6.38. So, what's going on here? Is it just my lack of git skills that are making this difficult? Thanks, Phil.
Labels (1)
0 Kudos
4 Replies

524 Views
rlorriaux
Contributor I

Pro Git (http://progit.org/book/) is one of the best resources for beginners. The man pages might be difficult to grasp at first.

0 Kudos

524 Views
PhilEndecott
Contributor II
> git branch -a > git checkout -t origin/imx_2.6.35_11.05.01 Well I did something like that. (Except that would be the 2.6.35 kernel. I want something new.) Can anyone recommend any git documentation that will teach syntax to that level of sophistication? I have encountered various git books, which stop short of that sort of thing, and the man pages, which just define things in terms of other jargon...
0 Kudos

524 Views
XXiao1z
Contributor III

right, do something like

git branch -a

git checkout -t origin/imx_2.6.35_11.05.01

will get you to the imx branch

 

it pains me that i could not reply via email, each time i have to visit the forum to reply, very inconvenient.

0 Kudos

524 Views
rlorriaux
Contributor I

The git repository is based on the mainline kernel, so you will see different tags and branches that pertain to the mainline only (there is little mx5 code there).

You are right, you will need to check out the different mx* tags. They correspond to the different releases.

0 Kudos