All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Matt Porter <mporter@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Jon Hunter <jon-hunter@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP baseline test results for v3.7-rc2
Date: Thu, 25 Oct 2012 07:14:23 -0700	[thread overview]
Message-ID: <87d30663ls.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20121023211151.GF1855@beef> (Matt Porter's message of "Tue, 23 Oct 2012 17:11:51 -0400")

Matt Porter <mporter@ti.com> writes:

> On Tue, Oct 23, 2012 at 02:03:43PM -0700, Kevin Hilman wrote:
>> Matt Porter <mporter@ti.com> writes:
>> 
>> [...]
>> 
>> > Ok, very quick update...no need to mess around with the eeprom. I just
>> > received the official word on what will be supported. Since A2 is
>> > pre-release, simply go to http://beagleboard.org/support/rma and fill
>> > out the form to have it replaced with the current revision (A6).
>> >
>> > This applies to *anyone* that received a pre-release A2 board.
>> 
>> Hmm, doesn't seem the RMA people are aware of this.  They just rejected
>> my request since it's not a "hardware related issue":
>> 
>>    Kevin,
>> 
>>    We only work with hardware related issue here. BeagleBone revision A2
>>    was not officially released. We recommend you to work with the
>>    community for support in Uboot. You can post your questions at the
>>    BeagleBoard Google Groups:
>>    https://groups.google.com/forum/?fromgroups=#!forum/beagleboard
>> 
>>    Regards,
>>    RMA Team
>
> That's sad considering the beagleboard.org/BeagleBone hardware designer
> specifically said they would be replaced via this route. *sigh*. Ok, I'll
> go back and share this with him.

Just and update...

Something happened behind the scenes (thanks Matt) and they've accepted
my RMA request.  I'll be sending back my board in order to get a new
one.

Thanks,

Kevin


WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc2
Date: Thu, 25 Oct 2012 07:14:23 -0700	[thread overview]
Message-ID: <87d30663ls.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20121023211151.GF1855@beef> (Matt Porter's message of "Tue, 23 Oct 2012 17:11:51 -0400")

Matt Porter <mporter@ti.com> writes:

> On Tue, Oct 23, 2012 at 02:03:43PM -0700, Kevin Hilman wrote:
>> Matt Porter <mporter@ti.com> writes:
>> 
>> [...]
>> 
>> > Ok, very quick update...no need to mess around with the eeprom. I just
>> > received the official word on what will be supported. Since A2 is
>> > pre-release, simply go to http://beagleboard.org/support/rma and fill
>> > out the form to have it replaced with the current revision (A6).
>> >
>> > This applies to *anyone* that received a pre-release A2 board.
>> 
>> Hmm, doesn't seem the RMA people are aware of this.  They just rejected
>> my request since it's not a "hardware related issue":
>> 
>>    Kevin,
>> 
>>    We only work with hardware related issue here. BeagleBone revision A2
>>    was not officially released. We recommend you to work with the
>>    community for support in Uboot. You can post your questions at the
>>    BeagleBoard Google Groups:
>>    https://groups.google.com/forum/?fromgroups=#!forum/beagleboard
>> 
>>    Regards,
>>    RMA Team
>
> That's sad considering the beagleboard.org/BeagleBone hardware designer
> specifically said they would be replaced via this route. *sigh*. Ok, I'll
> go back and share this with him.

Just and update...

Something happened behind the scenes (thanks Matt) and they've accepted
my RMA request.  I'll be sending back my board in order to get a new
one.

Thanks,

Kevin

  reply	other threads:[~2012-10-25 14:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 21:26 OMAP baseline test results for v3.7-rc2 Paul Walmsley
2012-10-20 21:26 ` Paul Walmsley
2012-10-21 17:06 ` Paul Walmsley
2012-10-21 17:06   ` Paul Walmsley
2012-10-22 16:10 ` Jon Hunter
2012-10-22 16:10   ` Jon Hunter
2012-10-22 17:17   ` Paul Walmsley
2012-10-22 17:17     ` Paul Walmsley
2012-10-22 17:18     ` Paul Walmsley
2012-10-22 17:18       ` Paul Walmsley
2012-10-22 16:28 ` Jon Hunter
2012-10-22 16:28   ` Jon Hunter
2012-10-22 16:38   ` Tony Lindgren
2012-10-22 16:38     ` Tony Lindgren
2012-10-23 19:34     ` Paul Walmsley
2012-10-23 19:34       ` Paul Walmsley
2012-10-22 18:35   ` Paul Walmsley
2012-10-22 18:35     ` Paul Walmsley
2012-10-22 18:36     ` Paul Walmsley
2012-10-22 18:36       ` Paul Walmsley
2012-10-22 18:50       ` Jon Hunter
2012-10-22 18:50         ` Jon Hunter
2012-10-22 18:48     ` Jon Hunter
2012-10-22 18:48       ` Jon Hunter
2012-10-23  1:53       ` Matt Porter
2012-10-23  1:53         ` Matt Porter
2012-10-23  3:15         ` Paul Walmsley
2012-10-23  3:15           ` Paul Walmsley
2012-10-23  4:57           ` Paul Walmsley
2012-10-23  4:57             ` Paul Walmsley
2012-10-23 12:24           ` Matt Porter
2012-10-23 12:24             ` Matt Porter
2012-10-23 13:11             ` Matt Porter
2012-10-23 13:11               ` Matt Porter
2012-10-23 21:03               ` Kevin Hilman
2012-10-23 21:03                 ` Kevin Hilman
2012-10-23 21:11                 ` Matt Porter
2012-10-23 21:11                   ` Matt Porter
2012-10-25 14:14                   ` Kevin Hilman [this message]
2012-10-25 14:14                     ` Kevin Hilman
2012-10-23  1:04 ` Kevin Hilman
2012-10-23  1:04   ` Kevin Hilman
2012-10-23 18:19   ` Kevin Hilman
2012-10-23 18:19     ` Kevin Hilman
2012-10-24  9:01     ` Igor Grinberg
2012-10-24  9:01       ` Igor Grinberg

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=87d30663ls.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mporter@ti.com \
    --cc=paul@pwsan.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.