All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Romero <xavinux@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Yi TZ Li <shliyi@cn.ibm.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC on Raspberry PI 3.
Date: Fri, 13 Oct 2017 11:02:17 -0300	[thread overview]
Message-ID: <CAEX+82L4mdooB_j6asHYdKmr=FRM1NuZJX3dVy2W+7fZpJb2vw@mail.gmail.com> (raw)
In-Reply-To: <1507870562.5452.195.camel@aj.id.au>

> Ah I wasn't talking about anything in particular, just that we should
> be able to improve our documentation from the questions you ask as you
> try to get OpenBMC working on the Raspberry Pi

So, will have to wait till the bug I've reported is fixed to continue
working with OpenBMC on Raspberry, nothing else I can do with my RPI
and obmc?

> But regarding the documentation, have you read through the docs repository at all?

Yes, I have check the documentation.

Javier Romero
E-mail: xavinux@gmail.com
Skype: xavinux



2017-10-13 1:56 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
> On Wed, 2017-10-11 at 16:09 -0300, Javier Romero wrote:
>> > Great! I look forward to you helping us improve our documentation and
>> > on-boarding of contributors. It might be rocky but it should help those
>> > coming along in the future.
>>
>> A starting point to start my contribution, so, how can I help on this?
>
> Ah I wasn't talking about anything in particular, just that we should
> be able to improve our documentation from the questions you ask as you
> try to get OpenBMC working on the Raspberry Pi. But regarding the
> documentation, have you read through the docs repository at all?
> Contributions are certainly welcome there:
>
> https://github.com/openbmc/docs/
>
> Cheers,
>
> Andrew

      reply	other threads:[~2017-10-13 14:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 15:38 OpenBMC on Raspberry PI 3 Javier Romero
2017-10-06 16:59 ` Rick Altherr
2017-10-06 21:28   ` Andrew Jeffery
2017-10-06 23:02     ` Javier Romero
2017-10-08  4:45       ` Javier Romero
2017-10-08 12:44         ` Andrew Jeffery
2017-10-09  2:57           ` Javier Romero
2017-10-09  6:41             ` Andrew Jeffery
2017-10-09  9:39               ` Yi TZ Li
2017-10-09 16:09                 ` Javier Romero
2017-10-10  0:14                   ` Andrew Jeffery
2017-10-10 14:01                     ` Javier Romero
2017-10-11  3:05                       ` Andrew Jeffery
2017-10-11 19:09                         ` Javier Romero
2017-10-13  4:56                           ` Andrew Jeffery
2017-10-13 14:02                             ` Javier Romero [this message]

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='CAEX+82L4mdooB_j6asHYdKmr=FRM1NuZJX3dVy2W+7fZpJb2vw@mail.gmail.com' \
    --to=xavinux@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=shliyi@cn.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.