I've not seen anywhere that ro.hardware gets set based on build.prop. init
sets ro.hardware based on the "Hardware" entry in /proc/cpuinfo (or an
optional kernel command line argument), which is not based on a particular
Android build, but underlying CPU arch. When building Android for
different devices, it seems like this introduces an additional dependency
on Android's build to make sure you install the fstab file with the
appropriate name. Why not just leave the name "vold.fstab"?
On Tuesday, February 4, 2014 10:39:09 AM UTC-5, rishi gupta wrote:
>
> In simple terms, ro.hardware is constant value whose value can be seen
> from build.prop.
> ro.hardware is mainly used for setting many properties, configuration
> files etc.
>
>
> On Monday, February 3, 2014 8:37:36 PM UTC+5:30, Kyle Russell wrote:
>>
>> Why did vold switch from loading the filename "vold.fstab" to
>> "fstab.${ro.hardware}"? It seems like there's only one fstab file that
>> ever gets loaded, and it's difficult to determine the "ro.hardware"
>> property value during a build, which is when you need to know the filename
>> to install the fstab file into an image. (In other words, the filename
>> change seems to introduce more variability, especially during the build,
>> that doesn't really buy anything.) Can anyone help explain?
>>
>
--
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
---
You received this message because you are subscribed to the Google Groups
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
