Joel, actually I have no idea. I just thought there is method
analogue, or somebody will point me to mailbox API
2015-06-01 22:44 GMT+03:00 Joel Sherrill :
>
>
> On 6/1/2015 2:32 PM, Yurii Shevtsov wrote:
>>
>> I have this lines in FreeBSD driver:
>>| bcm2835_mbox_set_power_state(dev, BCM2835_
On 6/1/2015 2:32 PM, Yurii Shevtsov wrote:
I have this lines in FreeBSD driver:
| bcm2835_mbox_set_power_state(dev, BCM2835_MBOX_POWER_ID_USB_HCD, TRUE);
How should I replace it?
What does that do? Without knowing the impact of that setting,
it is hard to make a statement.
Thanks in adv
It's using the mailbox property channel to communicate with the videocore. I've
noted down all available properties and the addresses used in a header file but
not yet implemented all of them. I'm working on it this week. If you need this,
you may put some marks here and I'll send a patch for t
I have this lines in FreeBSD driver:
| bcm2835_mbox_set_power_state(dev, BCM2835_MBOX_POWER_ID_USB_HCD, TRUE);
How should I replace it?
Thanks in advance)
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
- Gedare Bloom schrieb:
> On Sat, May 30, 2015 at 11:59 AM, Sebastian Huber
[...]
> > @@ -577,6 +602,9 @@ typedef struct {
> > * This structure defines floating point context area.
> > */
> > typedef struct {
> > +#if defined(SPARC_USE_SAFE_FP_SUPPORT)
> > + char dummy_to_make_the_works
Hi Saurabh,
Please try to figure out how to fix the compile-error. You can see
that the problem occurs in the #ifdef'd STRICT_ORDER_MUTEX_CODE, so
that makes sense why others have not observed the same issue. It
appears you will have to reconcile the new _Thread_Change_priority
arguments with what
On Sat, May 30, 2015 at 11:59 AM, Sebastian Huber
wrote:
> The SPARC ABI is a bit special with respect to the floating point context.
> The complete floating point context is volatile. Thus from an ABI point
> of view nothing needs to be saved and restored during a context switch.
> Instead the f
