build: Document why some drivers are disabled
This avoids confusion when looking at the build logs
This commit is contained in:
parent
45fb6d7908
commit
bb66780cb5
1 changed files with 2 additions and 2 deletions
|
@ -309,7 +309,7 @@ fi
|
||||||
if test x$enable_upeke2 != xno ; then
|
if test x$enable_upeke2 != xno ; then
|
||||||
AC_MSG_NOTICE([** upeke2 driver enabled])
|
AC_MSG_NOTICE([** upeke2 driver enabled])
|
||||||
else
|
else
|
||||||
AC_MSG_NOTICE([ upeke2 driver disabled])
|
AC_MSG_NOTICE([ upeke2 driver disabled (handled by upektc_img driver)])
|
||||||
fi
|
fi
|
||||||
if test x$enable_upektc != xno ; then
|
if test x$enable_upektc != xno ; then
|
||||||
AC_MSG_NOTICE([** upektc driver enabled])
|
AC_MSG_NOTICE([** upektc driver enabled])
|
||||||
|
@ -334,7 +334,7 @@ fi
|
||||||
if test x$enable_fdu2000 != xno ; then
|
if test x$enable_fdu2000 != xno ; then
|
||||||
AC_MSG_NOTICE([** fdu2000 driver enabled])
|
AC_MSG_NOTICE([** fdu2000 driver enabled])
|
||||||
else
|
else
|
||||||
AC_MSG_NOTICE([ fdu2000 driver disabled])
|
AC_MSG_NOTICE([ fdu2000 driver disabled (not ported)])
|
||||||
fi
|
fi
|
||||||
if test x$enable_aes1610 != xno ; then
|
if test x$enable_aes1610 != xno ; then
|
||||||
AC_MSG_NOTICE([** aes1610 driver enabled])
|
AC_MSG_NOTICE([** aes1610 driver enabled])
|
||||||
|
|
Loading…
Reference in a new issue