**** BEGIN LOGGING AT Sun Apr 29 02:59:58 2012 Apr 29 05:02:53 i take it that the fat.ko and vfat.ko for my marvell arm processor is the bootloader so what does .ko stand for? Apr 29 05:07:27 ok, thanks for the help i found out .ko means kernel object file Apr 29 05:09:31 so does fat.ko seach the input/output and vfat.ko point to the actual OS Apr 29 05:10:00 or vice-versa Apr 29 05:12:07 happydays, fat.ko doesn't have support for long file names Apr 29 05:12:10 while vfat does Apr 29 05:12:21 fat is only 7.3 file names Apr 29 05:16:37 scientes: ok but for an arm processor you wouldn't need much anyway Apr 29 05:16:51 happydays, it has nothing to do with the processor Apr 29 05:17:11 like, a mobile phone uses 7.3 safe file names Apr 29 05:17:16 **digital camera Apr 29 05:17:21 when it uses the fat filesystem Apr 29 05:17:48 doesn't it act as a bootloader for the arm? Apr 29 05:18:05 happydays, that doesn't concern the kernel Apr 29 05:18:15 thats uboot code, if you are using that sort ofsetup Apr 29 05:18:27 (my sheevaplug just uses a flat uImage partition, and then ubifs) Apr 29 05:18:29 oh Apr 29 05:18:41 forgot Apr 29 05:18:44 sure you can also access i from linux Apr 29 05:19:00 but i dont have any comp with that sort of bootloader Apr 29 05:20:46 fat is a VERY simple filesystem Apr 29 05:20:55 both with and without long file names Apr 29 05:21:53 cool ok thanks Apr 29 05:22:05 and for that reason it appears in alot of embedded devices Apr 29 05:22:12 ...and bootloaders Apr 29 05:30:55 i was just running my arm machine got side track on what i was doing and completely forgot about the uboot cause i got into the machine at the password and not the boot lol Apr 29 05:39:05 BTW sheevaplug's are great inexpensive devices great for learning the in's and out's of embedded systems **** ENDING LOGGING AT Mon Apr 30 02:59:58 2012