Hi,
linaro-android-media-create --dev option is now using "mx53loco" parameter for
i.MX53 boards. This changes is available on the bzr repository and will be part
of 2011.10 release. Please, update your scripts that are using the deprecated
"iMX53" value.
Cheers,
--
Fathi Boudra
Linaro Release M
Hi,
A document describing how to release Linaro components has been added:
http://wiki.linaro.org/Process/ReleaseComponents
If you release Linaro components, please take a look.
Feedback is welcome to improve the document.
Cheers,
--
Fathi Boudra
Linaro Release Manager | Validation Project Mana
On 11 October 2011 06:08, Ricardo Salveti wrote:
> On Mon, Oct 10, 2011 at 12:47 PM, David Zinman
> wrote:
>> Hi,
>>
>> This is a mail sent to remind you the coming release dates:
>>
>> * Linaro 11.10 components release is October 20nd, 2011.
>> * Linaro 11.10 RC images is October 24th, 2011.
On Mon, Oct 10, 2011 at 12:47 PM, David Zinman wrote:
> Hi,
>
> This is a mail sent to remind you the coming release dates:
>
> * Linaro 11.10 components release is October 20nd, 2011.
> * Linaro 11.10 RC images is October 24th, 2011.
> * Linaro 11.10 release is October 27th, 2011.
>
> Componen
Status report in detail
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/WeeklyReport
Last meeting minutes:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2011-10-05
== Highlights ==
- Planning done for the 1110. Please check the status report link above
for details
- U
Status report:
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/WeeklyReport
Last meeting minutes are included as IRC logs in
https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-10-04
== Highlights ==
- 1110 Blueprints planned. See the status report (link above) for
Enclosed please find the link to the Weekly Status report
for the Toolchain working group for the week ending 2011-10-07
== Meeting Minutes ==
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-10-03
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-10-06
== Weekly Status
On 6 October 2011 10:07, Andy Green wrote:
>
>
> On 6 October 2011 02:36, Tim Bird wrote:
>
>> On 10/05/2011 08:37 AM, Andy Green wrote:
>>
>> > Another side-issue is we are also looking at refactoring the
>> > Androidization patchset into topic branches, at the moment they're kind
>> > of refle
On Mon, Sep 26, 2011 at 03:48:09PM +0100, Pawel Moll wrote:
> > So I guess it must be no SATA because of broken PCI,
>
> True.
>
> > no MMC because of FPGA bugs (now fixed),
>
> Work-arounded ;-) (hopefully really fixed in near future).
>
> > no CF card because of (?).
>
> CF usability depen
Hi,
This is a mail sent to remind you the coming release dates:
* Linaro 11.10 components release is October 20nd, 2011.
* Linaro 11.10 RC images is October 24th, 2011.
* Linaro 11.10 release is October 27th, 2011.
Components release will be announced this week.
The release dates and deliver
On 09/23/2011 05:00 PM, Andy Doan wrote:
On 09/23/2011 06:51 AM, Turgis, Frederic wrote:
Hi,
Very cool. I've added this to the wiki:
https://wiki.linaro.org/Resources/HowTo/LTTng
Good idea !
I could move and reference page under
https://wiki.linaro.org/Platform/DevPlatform/Tools if peopl
On Mon, Oct 10, 2011 at 02:22:05PM +0200, Alexander Sack wrote:
> On Mon, Oct 10, 2011 at 2:08 PM, Loïc Minier wrote:
>
> > On Mon, Oct 10, 2011, Deepti Kalakeri wrote:
> > > 1) The board on which the hwpack can be booted
> > > 2) The hwpack creation timestamp includes the date in mmdd format
Hello Alexander,
Oops! I am sorry if I have misunderstood the BP
https://blueprints.launchpad.net/linaro-ci/+spec/improve-hwpack-names.
If we check the Acceptance criteria, it says
"Acceptance: The new name of hwpack generated by the linaro-hwpack-replace
contains the defconfig information."
If
On Mon, Oct 10, 2011 at 2:30 PM, Shawn Guo wrote:
>> +The example 8x8 PGA package above will have pin numbers 0 thru 63 assigned
>> to
>> +its physical pins. It will name the pins { A1, A2, A3 ... H6, H7, H8 } using
>> +pinctrl_register_pins_[sparse|dense]() and a suitable data set as shown
>
>
On Mon, Oct 10, 2011 at 2:08 PM, Loïc Minier wrote:
> On Mon, Oct 10, 2011, Deepti Kalakeri wrote:
> > 1) The board on which the hwpack can be booted
> > 2) The hwpack creation timestamp includes the date in mmdd format
> along
> > with the time in hhmm format.
> >
> > The hwpack name does no
On Mon, Oct 10, 2011 at 10:23:53AM +0200, Linus Walleij wrote:
> On Sun, Oct 9, 2011 at 11:36 AM, Shawn Guo wrote:
>
> >> + * @hog_on_boot: if this is set to true, the regulator subsystem will
> >> itself
> > ^
> > s/regulator/pinmux?
>
> Y
On Mon, Oct 10, 2011, Deepti Kalakeri wrote:
> 1) The board on which the hwpack can be booted
> 2) The hwpack creation timestamp includes the date in mmdd format along
> with the time in hhmm format.
>
> The hwpack name does not include any defconfig related information, which
> was used to bu
2011/10/10 Linus Walleij :
> From: Linus Walleij
>
> This adds a driver for the U300 pinmux portions of the system
> controller "SYSCON". It also serves as an example of how to use
> the pinmux subsystem. This driver also houses the platform data
> for the only supported platform.
>
> This deletes
2011/10/10 Linus Walleij :
> On Sat, Oct 8, 2011 at 11:09 AM, Barry Song <21cn...@gmail.com> wrote:
>>> +static void __init u300_pmx_dumpregs(struct u300_pmx *upmx)
>>> +{
>>> + u16 regval;
>>> + int i;
>>> +
>>> + for (i = 0; i < ARRAY_SIZE(u300_pmx_registers); i++) {
>>> +
Hello,
I am working on improving the hwpack names delivered by the Linaro Kernel
Continuous Integration.
To start on this I needed inputs from the kernel team.
currently the hwpack containing the newly built kernel debian package is
named for example as
hwpack_linaro-panda_20111004-1126_armel_sup
On Sun, Oct 9, 2011 at 11:36 AM, Shawn Guo wrote:
>> + * @hog_on_boot: if this is set to true, the regulator subsystem will itself
> ^
> s/regulator/pinmux?
Yep!
>> +#endif /* !CONFIG_PINCTRL */
>
> s/!CONFIG_PINCTRL/CONFIG_PINMUX?
Yep!
F
2011/10/9 tommy.hong :
> [Barry]
>>is this a debug information or do you want it to be in mainline?
>>
> Hi,Barry,should dumpregs function need "CONFIG_XXX_DEBUG" when probe ?and if
> driver meet some issue or error,we can use dumpregs to trace?
You can add any debug stuff you want if it helps dev
On Sat, Oct 8, 2011 at 11:09 AM, Barry Song <21cn...@gmail.com> wrote:
>> +static void __init u300_pmx_dumpregs(struct u300_pmx *upmx)
>> +{
>> + u16 regval;
>> + int i;
>> +
>> + for (i = 0; i < ARRAY_SIZE(u300_pmx_registers); i++) {
>> + regval = readw(upmx->virtba
23 matches
Mail list logo
